The component identifier is RSN_ISRCH. The module ID halfword is X'5B8D'.
The global reason codes:
| Value | Description |
|---|---|
| |
RSN_ISRCH_Found_Greater An index search has resulted in a record greater than the key. Probable cause: The index was searched using a key supplied by the caller. This is not necessarily considered an error. Action: The caller of the Index Manager should be aware of the reason code that is returned. This reason code is normally associated with Generic_Read or Generic_Delete searches. |
| |
RSN_ISRCH_Found_Equal An index search has resulted in an exact match. Probable cause: The index was searched using a key supplied by the caller. This is not necessarily considered an error, unless the caller didn't expect to find the record. Action: The caller of the Index Manager should be aware of the reason code that is returned. If this is a read or update request , this reason is to be expected. If this is a insert or write request, this reason could be a cause for concern. |
| |
RSN_ISRCH_SIR_Not_Found An index search has failed to find a record. Probable cause: The index was searched using a key supplied by the caller. This is not necessarily considered an error unless the caller did expect to find the record. Action: The caller of the Index Manager should be aware of the reason code that is returned. If this is a insert or write request, this reason is to be expected. If this is a read or delete request, this reason could be a cause for concern. |
| |
RSN_ISRCH_Invalid_Cursor While processing an index search request, GFUISRCH, found the cursor that was passed in from the caller was not valid. Probable cause: An unusual error occurred in the calling program's logic. This condition must be corrected. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM® Support. |
| |
RSN_ISRCH_Unexpected_Record_Type While searching an index, GFUISRCH will check the index page structure for validity. The index page was found to be invalid. Probable cause: The index page could be damaged from a previous error. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| |
RSN_ISRCH_Index_Page_Damaged The index page was found to be invalid. The index page's low threshold key is not consistent with the key in the parent page's down pointer Probable cause: The index page could be damaged from a previous error. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
The local reason codes:
| Value | Description |
|---|---|
| RSN_ISRCH + X'100' | RSN_ISRCH_Internal_Logic_Error Internal error in Index Read Management Functions (IRF) code. A logical error was detected while processing records within a directory's index page. Probable cause: The index page could be damaged from a previous error. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| RSN_ISRCH + X'101' | RSN_ISRCH_Serialize_Error GFUISRCH found an IBlock for an index page that is marked for update when it should be marked as read. Another thread is updating an index while this thread is attempting to search the index. Probable cause: The caller of the Index Manager should ensure proper serialization before a call to the Index Manager. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| RSN_ISRCH + X'102' | RSN_ISRCH_IO_Error GFUISRCH found an an inconsistent index structure. An additional call to check for a write protect error indicates that there was an I/O error during write protect. Probable cause: The use of HFS should ensure that a HFS did not violate a HFS data set sharing rule. Action: Check to see if the HFS was mounted on two systems at the same time. |
| RSN_ISRCH + X'103' | RSN_ISRCH_Lvl_GT_Parent The index page was found to be invalid. The index page's low threshold key is not consistent with the key in the parent page's down pointer. Probable cause: The index page could be damaged from a previous error. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| RSN_ISRCH + X'104' | RSN_ISRCH_Routing_Key_Error An HFS directory's index page was found to be invalid. The index page's low threshold key is not consistent with the key in the parent page's down pointer. Either the in-storage data representing the index is invalid, or the data as it resides on disk is invalid. Probable cause: The index page could be damaged from a previous error. Action: In some cases, an unmount and remount will clear the problem if it hasn't hardened on disk; otherwise, the HFS will have to be restored from a good backup, or recreated. Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| RSN_ISRCH + X'105' | RSN_ISRCH_Invalid_VPTVFN While processing the Attribute Directory IBlocks for file system, a call is made to Locate_AD_Page to obtain the VPT_VFN for the assigned RPN. Locate_AD_Page returned a VPT_VFN value of zero. This means that the RPN is not a valid value. Probable cause: This is a logic error in HFS AD page allocation. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| RSN_ISRCH + X'106' | RSN_ISRCH_Negative_RPN_On_Disk While processing the Attribute Directory IBlocks for the file system, an index page's routing node was found to have a relative page number (RPN) with a negative value. This is a temporary RPN that should be resolved during the file system sync operation. Probable cause: This is a logic error in GFUIARPN where all temporary RPNs are assigned a real RPN value before writing the index page to disk. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| RSN_ISRCH + X'107' | RSN_ISRCH_Deleted_Page_Found While processing the Attribute Directory IBlocks for the file system, a call is made to Locate_AD_Page to obtain the VPT_VFN for the assigned RPN. Locate_AD_Page returned a VPT_VFN value of zero. This means that the RPN is not a valid value. Probable cause: This is a logic error in HFS Attribute Directory (AD) page allocation. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| RSN_ISRCH + X'108' | RSN_ISRCH_Internal_Error While processing an index search request, GFUISRCH found an unusual programming logic condition. Probable cause: An unusual error occurred in the program's logic. This condition must be corrected. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| RSN_ISRCH + X'109' | RSN_ISRCH_DSB_Chain_Error While processing an index search request, GFUISRCH attempted to free a data space buffer. The data space buffer was found to have an invalid DSB chain value. Probable cause: An unusual error occurred in the program's logic. This condition must be corrected. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| RSN_ISRCH + X'10A' | RSN_ISRCH_Root_Is_Damaged The root page was found to be invalid when that root page of an index was read from disk. Probable cause: The index page could be damaged from a previous error. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| RSN_ISRCH + X'10B' | RSN_ISRCH_Media_Error GFUISRCH found an inconsistent index structure. An additional call to check for a write protect error indicates that there was a MEDIA error during write protect. Probable cause: The use of the HFS should ensure that an HFS did not violate an HFS data set sharing rule. Action: Check to see if the HFS was mounted on two systems at the same time. |