Introduction to IBM i OmniFind Health Checker

This article describes a set of DB2 stored procedures that can be used by administrators to identify common problems related to OmniFind Text Search server for DB2 for i, so that issues with text search servers and text search indexes can be resolved quickly without the need for advanced support.

You Liang Wu (youliangwu@cn.ibm.com), IBM i OmniFind developer, IBM China

You Liang Wu photoYou Liang Wu joined IBM in 2010. He currently is working on the development for OmniFind Text Search Server for DB2 for i.



Nick Lawrence (ntl@us.ibm.com), Advisory Software Engineer, IBM China

Nick Lawrence photoNick Lawrence has worked on DB2 for i for twelve years. His responsibilities include full text search for DB2 and SQL/XML.



07 November 2011

Also available in Chinese

Introduction

OmniFind Text Search Server for DB2 for i (5733-OMF) is a no additional charge licensed product that was first released in IBM i 6.1. This product allows users to perform full text search on text DB2 columns using the CONTAINS and SCORE SQL built in functions. For example, if the search is for "the cat chased a mouse", the search would also find documents that contain the phrase "the cats were chasing some mice". In IBM i 7.1 the product added support for searching system objects not associated with a DB2 column, such as spooled files or IFS stream files. In the latest round of improvements, new stored procedures have been added to check the health of text search indexes and servers. This article covers those enhancements. You can get a general background for the OmniFind Text Search Server from the white paper included in the additional resources section of this article.

The OmniFind Text Search Server for DB2 for i health checker support provides a set of stored procedures that can be used to diagnose configuration problems with a text search server or index. These health checker stored procedures will verify if the text search servers or indexes are correctly functioning and return a report highlighting any problems that are detected.

The IBM OmniFind Text Search Server product itself also provides stored procedures for the most common administrative functions, which makes it very easy for users to create and maintain indexes. For example, the SYSPROC.SYSTS_CREATE() procedure can be called to create an index and the SYSPROC.SYSTS_UPDATE() procedure can be used to update an index. However, sometimes these administrative stored procedures calls fail with errors such as:

  • Unable to create an index due to limited authorities
  • Failure to start a text server because no Java J2SE is installed
  • The text search index doesn't include the latest data changes due to the automatic update scheduler has not started
  • The search of an index not functioning properly because the text search server was shut down by mistake

In these cases, the health checker procedures can be used to diagnose the problems with your IBM OmniFind installation. The stored procedure, SYSPROC.SYSTS_HC_USR_AUTH(), can be used to check if a user has necessary authorities to create an index. The SYSPROC.SYSTS_HC_GENERAL() procedure can be used to verify that all of the required software is installed. The SYSPROC.SYSTS_HC_IDX() procedure can be used to determine if there are any problems with an index configuration and the SYSPROC.SYSTS_HC_SVR() procedure can be used to analyze if a text search server is functioning correctly. All of these health checker procedures report warnings and errors by returning a stored procedure result set. The contents of this result set can be used by users to identify and fix the problem or provide detailed information to IBM Support personnel for advanced diagnosis.


Service Details

This new OmniFind health checker support is delivered with PTF SI44462 in IBM i 7.1. The health checker support requires the IBM Application Runtime Expert (ARE) for i product, which is part of IBM i OS (5770-SS1) in IBM i 7.1. Visit the IBM ARE Support website for information on the required software and fixes for installing the ARE product.


Checking User Authorities

The DB2 stored procedure SYSPROC.SYSTS_HC_USR_AUTH() is used to report problems with the authorities of the invoking user. A result set is returned from this stored procedure.

If the parameter INFO_TYPE is omitted, SYSPROC.SYSTS_HC_AUTH() returns warning and error messages if there are any.

The stored procedure checks the following common problems:

  • *EXECUTE permission on administrative stored procedures
  • User permission on administrative catalogs
  • Job control special authority (for starting servers)
  • Other required authorities

Syntax

>>SYSTS_HC_USER_AUTH(------------)-----------------><
                -----INFO_TYPE---

The schema qualifier is SYSPROC.

Parameter

INFO_TYPE

Specifies the information type to be returned. The data type of the parameter is CHAR(1), valid values are:

  • 'I' – returns "Info" messages only
  • 'W' – returns "Warning" messages only
  • 'E' – returns "Error" messages only
  • 'X' – returns "Warning" and "Error" messages
  • 'A' – returns all messages

Return Result

A result set is returned from the stored procedure. The result set is composed of the following columns:

  • TYPE – CHAR(1), the type of the message, i.e., 'I', 'W', or 'E'. The message types represents:
    • 'I' – Information message, it is not a warning or error
    • 'W' – Warning message, if not corrected, it may cause problems
    • 'E' – Error message, indicates an error is found. The error needs to be corrected for OmniFind to work correctly
  • CODE – INTEGER, the Info, Warning or Error code of the message. Code ranges are:
    • 100-299: information messages
    • 300-499: warning messages
    • 500-999: error messages
  • ITEM– VARCHAR(128), the specific item checked, e.g. SYSPROC.SYSTS_START() or QSYS2.SYSTEXTSERVERS.
  • MESSAGE – VARCHAR(512), the detailed Info, Warning or Error message.

Examples

To return all health checking results for the authorities of the invoking user:

CALL SYSPROC.SYSTS_HC_USR_AUTH('A')

Sample output is like this:

TYPECODEITEMMESSAGE
I104SYSTS_START()EXECUTE permission on SYSTS_START() is granted.
I104SYSTS_STARTEXECUTE permission on SYSTS_START is granted.
I104SYSTS_STOP()EXECUTE permission on SYSTS_STOP() is granted.
I104SYSTS_STOPEXECUTE permission on SYSTS_STOP is granted.
I104SYSTS_CREATEEXECUTE permission on SYSTS_CREATE is granted.
I104SYSTS_UPDATEEXECUTE permission on SYSTS_UPDATE is granted.
I104SYSTS_DROPEXECUTE permission on SYSTS_DROP is granted.
I104SYSTS_ALTEREXECUTE permission on SYSTS_ALTER is granted.
I104SYSTS_REMOVEEXECUTE permission on SYSTS_REMOVE is granted.
I202SYSTEXTDEFAULTSAuthority list on table SYSTEXTDEFAULTS is (Read: true, Add: true, Update: true, Delete: true, Execute: true).
I202SYSTEXTSERVERSAuthority list on table SYSTEXTSERVERS is (Read: true, Add: true, Update: true, Delete: true, Execute: true).
I202SYSTEXTINDEXESAuthority list on table SYSTEXTINDEXES is (Read: true, Add: true, Update: true, Delete: true, Execute: true).
I202SYSTEXTCOLUMNSAuthority list on table SYSTEXTCOLUMNS is (Read: true, Add: true, Update: true, Delete: true, Execute: true).
I202SYSTEXTCONFIGURATIONAuthority list on table SYSTEXTCONFIGURATION is (Read: true, Add: true, Update: true, Delete: true, Execute: true).
I202SYSTEXTSERVERHISTORYAuthority list on table SYSTEXTSERVERHISTORY is (Read: true, Add: true, Update: true, Delete: true, Execute: true).
I205*JOBCTL"*JOBCTL" authority is granted.

To return the warning and error checking results for the authorities of the invoking user:

CALL SYSPROC.SYSTS_HC_USR_AUTH()

Checking General Configurations

The DB2 stored procedure SYSPROC.SYSTS_HC_GENERAL() is used to check the general health of the OmniFind Text Search Server for DB2 for i product. The procedure checks the configuration of the product.

A result set is returned when the stored procedure has successfully completed. The result set reports issues with the product install or configuration that may need to be addressed by an administrator.

The following items are checked by this stored procedure:

  • The installation of required LPPs (ICU, Java, QSH and etc.)
  • PTFs that applied in the system
  • The OmniFind administrative stored procedures
  • The configuration of varyon and varyoff programs for Independent Auxiliary Storage Pools (iASP)
  • Administrative catalogs
  • OmniFind default values in QSYS2.SYSTEXTDEFAULTS

Syntax

>>SYSTS_HC_GENERAL(-------------- )---------------------><
		   ---INFO_TYPE-----
		   ---INFO_TYPE, AUTO_FIX-----

The schema qualifier is SYSPROC.

Parameters

INFO_TYPE

Specifies the information type to be returned, see INFO_TYPE in SYSTS_HC_AUTH().

AUTO_FIX

Reserved for future use only, type SMALLINT. Currently the value is required to be 0. The server will not automatically perform fixes.

If parameter list is null, all warning and error messages are returned.

Return Result

A result set is returned from the stored procedure. The result set is composed of the following columns:

  • TYPE – CHAR(1), the type of the message, see TYPE in SYSTS_HC_AUTH().
  • CODE – INTEGER, the Info, see CODE in SYSTS_HC_AUTH().
  • ITEM – VARCHAR(128), the specific item checked. For example: SYSPROC.SYSTS_START() or QSYS2.SYSTEXTSERVERS.
  • MESSAGE – VARCHAR(512), the detailed Info, Warning or Error message.

Examples

To take the general health checking and return all messages:

CALL SYSPROC.SYSTS_HC_GENERAL('A', 0)

Sample output is like this:

TYPECODEITEMMESSAGE
I106QShell LPP QShell is installed.
I106IBM i Portable Application Solutions Environment (IBM i PASELPP IBM i Portable Application Solutions Environment (IBM i PASE) is installed.
I106International Components for UnicodeLPP International Components for Unicode is installed.
I203J2SE 5.0 32 bit, 5770JV1, Option 8LPP J2SE 5.0 32 bit, 5770JV1, Option 8 not installed.
I203J2SE 5.0 64 bit, 5770JV1, Option 9LPP J2SE 5.0 64 bit, 5770JV1, Option 9 not installed.
I203J2SE 6.0 32 bit, 5770JV1, Option 11LPP J2SE 6.0 32 bit, 5770JV1, Option 11 not installed.
I203J2SE 6.0 64 bit, 5770JV1, Option 12LPP J2SE 6.0 64 bit, 5770JV1, Option 12 not installed.
I106J2SE 5.0 32 bit, 5761JV1, Option 8LPP J2SE 5.0 32 bit, 5761JV1, Option 8 is installed.
I106J2SE 5.0 64 bit, 5761JV1, Option 9LPP J2SE 5.0 64 bit, 5761JV1, Option 9 is installed.
I106J2SE 6.0 32 bit, 5761JV1, Option 11LPP J2SE 6.0 32 bit, 5761JV1, Option 11 is installed.
I106J2SE 6.0 64 bit, 5761JV1, Option 12LPP J2SE 6.0 64 bit, 5761JV1, Option 12 is installed.
I107SYSTS_ALTERStored procedure SYSTS_ALTER exists.
I107SYSTS_CREATEStored procedure SYSTS_CREATE exists.
I107SYSTS_DROPStored procedure SYSTS_DROP exists.
I107SYSTS_REMOVEStored procedure SYSTS_REMOVE exists.
I107SYSTS_REPRIMEINDEXStored procedure SYSTS_REPRIMEINDEX exists.
I107SYSTS_STARTStored procedure SYSTS_START exists.
I107SYSTS_STOPStored procedure SYSTS_STOP exists.
I107SYSTS_UPDATEStored procedure SYSTS_UPDATE exists.
I107SYSTS_VALIDITYCHECKStored procedure SYSTS_VALIDITYCHECK exists.
I204SYSTS_START()External PGM for stored procedure SYSTS_START() exists.
I204SYSTS_STARTExternal PGM for stored procedure SYSTS_START exists.
I204SYSTS_STOP()External PGM for stored procedure SYSTS_STOP() exists.
I204SYSTS_STOPExternal PGM for stored procedure SYSTS_STOP exists.
I204SYSTS_CREATEExternal PGM for stored procedure SYSTS_CREATE exists.
I204SYSTS_UPDATEExternal PGM for stored procedure SYSTS_UPDATE exists.
I204SYSTS_DROPExternal PGM for stored procedure SYSTS_DROP exists.
I204SYSTS_ALTERExternal PGM for stored procedure SYSTS_ALTER exists.
I204SYSTS_REMOVEExternal PGM for stored procedure SYSTS_REMOVE exists.
E554QDBTS_LISTINXSTSUser defined function QDBTS_LISTINXSTS is not installed.
I109QDBTSVRYONVary Program QDBTSVRYON registered.
I109QDBTSVRYOFVary Program QDBTSVRYOF registered.
I110CCSIDOmniFind System default value CCSID: Value = 1208, Type = 1.
I111CCSIDOmniFind system default value CCSID exists.
I110LANGUAGEOmniFind System default value LANGUAGE: Value = en_US, Type = 1.
I111LANGUAGEOmniFind system default value LANGUAGE exists.
I110FORMATOmniFind System default value FORMAT: Value = TEXT, Type = 1.
I111FORMATOmniFind system default value FORMAT exists.
I110UPDATEFREQUENCYOmniFind System default value UPDATEFREQUENCY: Value = NONE, Type = 1.
I111UPDATEFREQUENCYOmniFind system default value UPDATEFREQUENCY exists.
I110UPDATEMINIMUMOmniFind System default value UPDATEMINIMUM: Value = 1, Type = 1.
I111UPDATEMINIMUMOmniFind system default value UPDATEMINIMUM exists.
I110MINIMUMUPDATEINTERVALOmniFind System default value MINIMUMUPDATEINTERVAL: Value = 5, Type = 0.
I111MINIMUMUPDATEINTERVALOmniFind system default value MINIMUMUPDATEINTERVAL exists.
I110USEREXITTHREADSOmniFind System default value USEREXITTHREADS: Value = 0, Type = 1.
I111USEREXITTHREADSOmniFind system default value USEREXITTHREADS exists.
I110IGNOREEMPTYDOCSOmniFind System default value IGNOREEMPTYDOCS: Value = 1, Type = 1.
I111IGNOREEMPTYDOCSOmniFind system default value IGNOREEMPTYDOCS exists.
I110UPDATEAUTOCOMMITOmniFind System default value UPDATEAUTOCOMMIT: Value = 100, Type = 1.
I111UPDATEAUTOCOMMITOmniFind system default value UPDATEAUTOCOMMIT exists.
I110CJKSEGMENTATIONOmniFind System default value CJKSEGMENTATION: Value = NGRAM, Type = 1
I111CJKSEGMENTATIONOmniFind system default value CJKSEGMENTATION exists.
I113SYSTEXTDEFAULTSU1Constraint SYSTEXTDEFAULTSU1 is ok
I112SYSTEXTDEFAULTSTable SYSTEXTDEFAULTS is journaled.
I113SYSTEXTSERVERSPConstraint SYSTEXTSERVERSP is ok
I113SYSTEXTSERVERSU1Constraint SYSTEXTSERVERSU1 is ok
I113SYSTEXTSERVERALConstraint SYSTEXTSERVERAL is ok
I112SYSTEXTSERVERSTable SYSTEXTSERVERS is journaled.
I113SYSTEXTINDEXESPConstraint SYSTEXTINDEXESP is ok
I113SYSTEXTINDEXESU1Constraint SYSTEXTINDEXESU1 is ok
I113SYSTEXTINDEXEF1Constraint SYSTEXTINDEXEF1 is ok
I113SYSTEXTINDEXEF2Constraint SYSTEXTINDEXEF2 is ok
I112SYSTEXTINDEXESTable: SYSTEXTINDEXES is journaled.
I113SYSTEXTCOLUMNSPConstraint SYSTEXTCOLUMNSP is ok
I113SYSTEXTCOLUMNSF1Constraint SYSTEXTCOLUMNSF1 is ok
I112SYSTEXTCOLUMNSTable: SYSTEXTCOLUMNS is journaled.
I113SYSTEXTCONFIGURATIONConstraint SYSTEXTCONFIGURATION is ok
I113SYSTEXTCONFIGURATIONF0Constraint SYSTEXTCONFIGURATIONF0 is ok
I112SYSTEXTCONFIGURATIONTable: SYSTEXTCONFIGURATION is journaled.
I113SYSTEXTSERVERHISTORYU1Constraint SYSTEXTSERVERHISTORYU1 is ok
I112SYSTEXTSERVERHISTORYTable: SYSTEXTSERVERHISTORY is journaled.

To return all warning and error messages:

CALL SYSPROC.SYSTS_HC_GENERAL()

Checking Indexes

The DB2 stored procedure SYSPROC.SYSTS_HC_IDX() is used to check a particular text index or all indexes in the current Independent Auxiliary Storage Pool (IASP) group, depending on the parameters given. If a qualified index name is given, the health checking report applies to the particular index; otherwise, all text indexes in the IASP group will be checked. A result set is returned when the stored procedure is successfully completed. The stored procedure SYSPROC.SYSTS_HC_IDX_SN() performs the same function but accepts index schema and index name as its parameters.

A list of the items checked by this procedure are:

  • The base table for the index exists
  • The index, column and configuration items are correct in catalogs SYSTEXTINDEXES, SYSTEXTCOLUMNS and SYSTEXTCONFIGURATION
  • Records in SYSTEXTSERVERHISTORY are valid
  • The collection directory of the index exists, if the index is defined in a local server
  • The view for the index exists
  • The server associated with the index is active
  • The update scheduler is configured correctly
  • The insert, update and delete triggers exist on the based table for the index
  • The staging table for the index exists
  • The owner of the triggers, staging table and index view are consistent
  • The authorities of the index owner on the base table and administrative catalogs are correct
  • The authority of the index owner includes the ability to modify the job scheduler entry used for the scheduled update
  • The index owner has he special authority *JOBCTL..

Syntax

>>-SYSTS_HC_IDX(-------------- )------------------------><
		---INDEXSCHEMA, INDEXNAME, INFO_TYPE, AUTO_FIX
		---INDEXSCHEMA, INDEXNAME, INFO_TYPE
		---INFO_TYPE, AUTO_FIX
		---INFO_TYPE
>>SYSTS_HC_IDX_SN(INDEXSCHEMA,INDEXNAME)---------------><

The schema qualifier is SYSPROC.

Parameters

INFO_TYPE

Specifies the information type to be returned. See INFO_TYPE in SYSTS_HC_AUTH().

AUTO_FIX

Reserved for future use only. See AUTOFIX in SYSTS_HC_GENERAL().

INDEXSCHEMA

Specifies the schema of the index to be checked. The type of the parameter is VARCHAR(128) and CCSID 1208. The value must be a valid SQL name. The index schema parameter is case sensitive and will not be folded to upper case automatically.

INDEXNAME

Specifies the name of the index to be checked. The type of the parameter VARCHAR(128) and CCSID 1208. The value must be a valid SQL name. The index name is case sensitive and will not be folded to upper case automatically.

If parameter list is empty, health checking is applied to all existing indexes, warning and error messages are returned and no auto fixing is applied.

Return Result

A result set is returned from the stored procedure. The result set is composed of following columns:

  • ID – INTEGER, the index ID.
  • TYPE – CHAR(1), the type of the message, see TYPE in SYSTS_HC_AUTH().
  • CODE – INTEGER, the Info, see CODE in SYSTS_HC_AUTH().
  • ITEM – VARCHAR(128), the specific item checked, e.g. the staging table, the view for the index.
  • MESSAGE – VARCHAR(512), the detailed Info, Warning or Error message.

Examples

To check the index TESTSCHEMA.TESTINDEX, returning all messages, no auto fix applied:

CALL SYSPROC.SYSTS_HC_IDX('TESTSCHEMA', 'TESTINDEX', 'A', 0)

Sample output is like this:

IDTYPECODEITEMMESSAGE
10,608I128-The column entry for the index exists.
10,608I129-The config entry for the index exists.
10,608I130-The history entry for the index exists.
10,608I131-The base table of the index exists.
10,608I206-Unique or primary key constraint exists in the based table.
10,608I121-Server is active.
10,608I117-Server path is valid.
10,608W316-Automatic update for the index is not started.
10,608I123INSERTThe INSERT trigger exists.
10,608I124INSERTThe INSERT trigger is enabled.
10,608I123UPDATEThe UPDATE trigger exists.
10,608I124UPDATEThe UPDATE trigger is enabled.
10,608I123DELETEThe DELETE trigger exists.
10,608I124DELETEThe DELETE trigger is enabled.
10,608I132-The staging table of the index exists
10,608I112staging tableTable: staging table is journaled.
10,608I133-The view for the index exists.
10,608I126-The owners are consistent.
10,608I126-The owners are consistent.
10,608I126-The owners are consistent.
10,608I127Job SchedulerThe user has the permission on Job Scheduler Entry.
10,608I127the base tableThe user has the permission on the base table.
10,608I127SYSTEXTDEFAULTSThe user has the permission on SYSTEXTDEFAULTS.
10,608I127SYSTEXTSERVERSThe user has the permission on SYSTEXTSERVERS.
10,608I127SYSTEXTINDEXESThe user has the permission on SYSTEXTINDEXES.
10,608I127SYSTEXTCOLUMNSThe user has the permission on SYSTEXTCOLUMNS.
10,608I127SYSTEXTCONFIGURATIONThe user has the permission on SYSTEXTCONFIGURATION.
10,608I127SYSTEXTSERVERHISTORYThe user has the permission on SYSTEXTSERVERHISTORY.
10,608I205*JOBCTL"*OBJCTL" authority is granted.

To check the index TESTSCHEMA.TESTINDEX, returning only error messages:

CALL SYSPROC.SYSTS_HC_IDX('TESTSCHEMA', 'TESTINDEX', 'E')

To check all indexes and return warning and error messages:

CALL SYSPROC.SYSTS_HC_IDX()

Checking Servers

The DB2 stored procedure SYSTS_HC_SVR() is used to check the health of a specific local text server, or all local servers that have been configured. If a server ID is specified, the procedure checks only that text server, otherwise it checks all servers configured for the current Independent Auxiliary Storage Pool (IASP) group. A result set is returned from the stored procedure. The procedures SYSPROC.SYSTS_HC_SVR_T() and SYSPROC.SYSTS_HC_SVR_IT() perform the same function but accept different parameters for qualifying which servers are checked and what information is returned.

The stored procedure checks the following items for text servers:

  • Authentication token is valid
  • IP address is valid
  • Server path is valid
  • Server port is valid

For each active local server, additional checks are done to verify that the required server jobs are running and the server port can be contacted.

Syntax

>>SYSTS_HC_SVR(---------------)-----------------------><
		----SERVERID, INFO_TYPE, AUTO_FIX ----
		----SERVERID----
		----INFO_TYPE, AUTO_FIX----
>>SYSTS_HC_SVR_IT(SERVERID,INFO_TYPE)--------------------><
>>SYSTS_HC_SVR_T(INFO_TYPE)----------------------------><

The schema qualifier is SYSPROC.

Parameters

SERVERID

Specifies the identifier of the text server to be checked. The server identifier for a specific server can be obtained by using the IBM Systems Director Navigator for i. Using Director Navigator to obtain server information and status is discussed in the InfoCenter.

This information can also be obtained from the system catalogs with an SQL query like this:

SELECT SERVERID, SERVERNAME, SERVERPATH, ALIASNAME FROM QSYS2.SYSTEXTSERVERS;

INFO_TYPE

Specifies the information type to be returned, see INFO_TYPE in SYSTS_HC_AUTH().

AUTO_FIX

Reserved for future use only, see AUTO_FIX in SYSTS_HC_GENERAL().

Return Result

A result set is returned when the successful complete of the stored procedure. The result set is composed of following columns:

  • ID – INTEGER, the server ID.
  • TYPE – CHAR(1), the type of the message, seeTYPEin SYSTS_HC_AUTH().
  • CODE – INTEGER, the Info, Warning or Error code of the message, see CODE in SYSTS_HC_AUTH().
  • ITEM – VARCHAR(128), the specific item checked, generally not used in server checking since the MESSAGE gives very clear information.
  • MESSAGE – VARCHAR(512), the detailed Info, Warning or Error message.

Examples

To check the server with id 50 and return all messages:

CALL SYSPROC.SYSTS_HC_SRV(50, 'A', 0)

Sample output is like this:

IDTYPECODEITEMMESSAGE
50I117-Server path is valid.
50I116-Server token is valid.
50I118-Server name is valid.
50I119-Server port is valid.
50I114-Server jobs are ok.
50I115-Stellent jobs are ok.
50I120-Server is connectable.

To check server with id 50 and return warning and error messages.

CALL SYSPROC.SYSTS_HC_SRV(50)

Summary

The OmniFind health checker provides a set of DB2 stored procedures that can be invoked by users for checking general configurations, text servers and indexes. It can be used to return warning and/or error messages if there are any problems with the OmniFind Text Search Server for i. The information can then be used to understand the cause of a difficult problem quickly and take appropriate corrective action.


Resources

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into IBM i on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=IBM i, Information Management
ArticleID=769092
ArticleTitle=Introduction to IBM i OmniFind Health Checker
publish-date=11072011