The following reason codes are defined by the Index Manager.
| Value | Description |
|---|---|
| A02B | IMF_IRF_Logical_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. |
| A02E | IMF_Need_More_Fdbk_Space Feedback area does not have enough space for IMF to return the found index records. Probable cause: The callers to the Index Manager did not supply an adequately sized feedback area during a read of the HFS directory's index. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A030 | IMF_Duplicate Duplicate index record found. 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 calling program is attempting to insert a keyed-record into an HFS directory, but a record with that same key already resides in the directory. The record insert failed. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A033 | IMF_Index_Page_Damaged During the search operation of a HFS index, an inconsistent index structure was detected. 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. |
| A03B | IMF_Page_Not_Found During the search operation of a HFS index, an index page could not be found. Probable cause: The index page could be damaged from a prior index update operation. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A049 | IMF_Zero_Key_Addr The address of the index key was found to be zero. Probable cause: The caller of the Index Manager failed to provide an index key. This is required on all index read and delete operations. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A04A | IMF_Zero_SIR_Addr The address of the SIR was found to be zero. Probable cause: The caller of the Index Manager failed to provide a SIR. This is required on all index insert, write, and update operations. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A04B | IMF_Zero_Cursor_Addr The address of the index cursor was found to be zero. Probable cause: The caller of the Index Manager failed to provide a cursor. This is required on all index generic- read operations. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A04C | IMF_Zero_Feedback_Addr The address of the feedback area was found to be zero. Probable cause: The caller of the Index Manager failed to provide a feedback area. This is required on all index read operations. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A04D | IMF_Invalid_Cursor The cursor does not have a valid eyecatcher. Probable cause: The caller of the Index Manager failed to provide a valid cursor. This is required on all index generic-read operations. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A04E | IMF_Invalid_Search_Mode Invalid search mode has been specified. Probable cause: The caller of the Index Manager failed to provide a search mode that is consistent with the type of index operation requested. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A054 | IMF_Inv_Gen_Search_Mode Invalid search mode has been with GENERIC keyword. Probable cause: The caller of the Index Manager failed to provide a search mode that is consistent with the type of index operation requested. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A074 | IMF_Unx_Record_Type Unexpected record type detected while reading the contents of an 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. |
| A076 | IMF_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. |
| A411 | IMF_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 did not expect to find the record. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A412 | IMF_Found_Less_Than An index search has resulted in a record less than the key. Probable cause: The index was searched using a key supplied by the caller. This is not necessarily considered an error. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A413 | IMF_Found_Greater_Than 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: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A414 | IMF_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: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A415 | IMF_Empty_Page A delete operation has emptied an index page. Probable cause: This is a normal condition that occurs during a record delete operation. This is an internal reason code that is passed from the index page record delete routine to its caller. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A416 | IMF_Partial_Gen_Del The end of the page was reached while performing a generic deletion. The operation may need to be continued in the next page. Probable cause: This is a normal condition that occurs during a record delete operation. This is an internal reason code that is passed from the index page record delete routine to its caller. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A417 | IMF_Update_Page_Full The requested update operation resulted in a record that was longer than the original and the new record would not fit in the page. A split must be done before the update can be performed. Probable cause: This is a normal condition that occurs during a record update operation. This is an internal reason code that is passed from the index page record update routine to its caller. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A418 | IMF_Feedback_Full There is not enough room in the provided feedback area to perform the requested function. Probable cause: The caller of IMF requested that the Index Manager read a record into the caller supplied feedback area. However, the feedback area is not large enough to hold the requested record. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A419 | IMF_At_End_Of_Page The position information now locates the end of a page. Probable cause: This is a normal condition that occurs during an index page record scan operation. This is an internal reason code that is passed from the index page record scan routine to its caller. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A41A | IMF_Insert_Page_Full An attempt was made to insert a record into a page where it would not fit. A split must be done to continue the operation. Probable cause: This is a normal condition that occurs during an index page record insert operation. This is an internal reason code that is passed from the index page record insert routine to its caller. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A41B | IMF_Try_Previous An index page scan should be attempted on the page that precedes the current one on the same level. Probable cause: The index was searched using a key supplied by the caller. This is an internal reason code that is passed from the index page search routine to its caller.This is not considered an error. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A41C | IMF_Try_Next An index page scan should be attempted on the page that follows the current one on the same level. Probable cause: The index was searched using a key supplied by the caller. This is an internal reason code that is passed from the index page search routine to its caller.This is not considered an error. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A41D | IMF_Insrt_End_of_Page An insert into a full page has been attempted. The insert tried to put a record at the end of the page. If the page has already been split as part of a related request, then the insert can be attempted in next page on the same level and this page does not need to be changed. Probable cause: This is a normal condition that occurs during an index page record insert operation. This is an internal reason code that is passed from the index page record insert routine to its caller. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A41E | IMF_Split_On_Reseg An resegment operation has has been attempted. It was not able to be performed because the resulting resegmented page would not fit in the existing page. A split must be done on the page. Probable cause: The index page was too full before the resegment operation was attempted. This is an error in the Index Manager program because each index page should have a sufficient amount of reserved space to accommodate the index page resegment operation. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A41F | IMF_Delete_Page_Full An attempt was made to delete a record from a compressed format page. The following record was front compressed relative to the to-be-deleted-record. The expanded key of the next record requires more space than is available in the page. A split must be performed. Probable cause: The index page was too full before the recompress operation was attempted. This is an error in the Index Manager program because each index page should have a sufficient amount of reserved space to accommodate the index page recompress operation. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A420 | IMF_Insert_Key_Out_Of_Order Attempt to insert record with key smaller than previous record. Probable cause: This is a programming logic error by the Index Manager. If the index was constructed correctly, then the index search and scan operation should create the positioning information to allow a record insert in the correct record sequence. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |
| A7F7 | IMF_Split_End_Of_Page A split occurred at the end of the full page. The full page is unchanged and does not need to be written. The new page has been initialized and contains no records. Probable cause: This is a normal condition that occurs during an index page record split operation. This is an internal reason code that is passed from the index page record split routine to its caller. Action: Save the output from the failing job, the SVC dump, and any logrec data set records for the error. Contact IBM Support. |