HP 3000 Manuals HP 3000 Manuals
Chapter 5 Error Messages and Their Causes This section lists error messages that you may encounter while using HP Search, along with the most likely reason that the message will be issued. NLS is not installed. (SRCHERR 10) CAUSE: You specified a pattern that has "special" characters, and NLS must be configured on your system to process them. ACTION: Either configure NLS on your system or don't include the following characters in your patterns: ( ) [ ] | - + * # @ ? or \. Specified language is not configured. (SRCHERR 20) CAUSE: The language HP Search is using to process your pattern has not been configured on your system. ACTION: This is an internal HP Search error. Please contact HP support; investigation is required. Until this is resolved, do not include the following characters in your patterns: ( ) [ ] | - + * # @ ? or \. Indirect file FILENAME does not exist. (SRCHERR 30) CAUSE: The indirect file "FILENAME" which was specified as"^FILENAME" does not exist in either the temporary or permanent file domains. ACTION: Check your file directory for the correct name of the desired file. Missing ) or ] operator in pattern "PATTERN." (SRCHERR 40) CAUSE: The pattern you specified in invalid. It contains either a ( or [ without the corresponding matching delimiter. ACTION: If you do not want the ( or [ to have special meaning, precede them with a backslash. If you do want the special meaning, the pattern must have a closing delimiter. Expected alphabetic characters in pattern "PATTERN." (SRCHERR 50) CAUSE: The pattern you specified does not have an alphabetic character where one is expected. ACTION: Inspect your pattern to make sure it is correct. If it is, please contact HP support; investigation is required. Pattern specified is incomplete, "PATTERN." (SRCHERR 60) CAUSE: Usually this is caused by the "*" or "+" characters in your pattern not being preceded by a valid repeatable character. For example, "a**" is invalid. ACTION: Inspect your pattern to make sure it is correct. If it is, please contact HP support; investigation is required. Invalid range operation specified in pattern "PATTERN." (SRCHERR 70) CAUSE: The range you have specified with the hyphen (-) is not between a valid pair. The first character must be lower than the second. For example, "a-z" is valid but "z-a" is not. ACTION: In most cases, simply reverse the characters on either side of the hyphen. Could not open indirect file FILENAME. (SRCHERR 80, FSERR nnn) CAUSE: The indirect pattern file "FILENAME", specified as "^FILENAME" exists, but could not be opened. The attempt to open the file resulted in file system error number nnn. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. Help command missing or misspelled. (SRCHERR 90) CAUSE: This is an internal HP Search error. ACTION: Please contact HP support; investigation is required. Nested indirect file FILENAME not used. (SRCHERR 100) CAUSE: A pattern in an indirect pattern file pointed to another indirect file. Only 1 level of indirect files is allowed for patterns. The search continues without using any patterns contained in "FILENAME". ACTION: If you want the patterns in "FILENAME" to be searched for, specify "FILENAME" on the HP Search command line or at a pattern prompt. Pattern exceeds 80 characters. Not used. (SRCHERR 110) CAUSE: You specified a pattern that has more than 80 characters, which is the maximum number allowed. ACTION: Modify the pattern to contain 80 characters or fewer. Too many patterns. Only first 16 used. (SRCHERR 120) CAUSE: You specified too many patterns for your search. The search will continue using only the first 16 valid patterns specified. ACTION: Specify another search exclusively for the patterns not included in the first search. Octal value out of valid character range in pattern "PATTERN." (SRCHERR 130) CAUSE: One of your patterns contained a percent sign followed by one or more octal digits. These octal digits were outside the allowable range. ACTION: Check the octal digit you specified against the one corresponding to the desired ASCII character. A valid range for characters is an octal value between 1 and 377. Also valid after the percent sign are the characters "x","s", and "d". Unrecognized character follows percent sign in pattern "PATTERN." (SRCHERR 140) CAUSE: One of your patterns contained a percent sign followed by an unrecognized character. The pattern with a caret (^) pointing to the unrecognized character is displayed following the error message. ACTION: Check the character after the percent sign and specify a valid one. A valid range for characters is an octal value between 1 and 377. Also valid after the percent sign are the characters "x","s", and "d". Pattern is too long for the NLMATCHINIT intrinsic, "PATTERN." (SRCHERR 160) CAUSE: HP Search uses an intrinsic called NLMATCHINIT to preprocess the patterns you specify. One of the patterns you have entered is too long for this intrinsic. ACTION: This is an internal HP Search error. Please contact HP support; investigation is required. A work-around is to shorten the specified pattern. File FILENAME does not exist. (SRCHERR 180) CAUSE: The file named "FILENAME" does not exist in either the temporary or permanent file domains and therefore cannot be searched. ACTION: Check your file directory for the correct name of the desired file. Could not open file FILENAME. (SRCHERR 190, FSERR nnn) CAUSE: The file named "FILENAME" exists, but could not be opened. The attempt to open the file resulted in file system error number nnn. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. Lockword violation on file FILENAME. (SRCHERR 200) CAUSE: The file named "FILENAME" could not be opened due to a missing or incorrect lockword. ACTION: Provide the correct lockword. Binary file FILENAME not processed. (SRCHERR 210) CAUSE: The file named "FILENAME" is a binary file, and HP Search does not search binary files. ACTION: Don't search binary files with HP Search. Maximum indirect levels exceeded by file FILENAME. (SRCHERR 220) CAUSE: Your search specification exceeded the eleven indirect levels allowed for file names. "FILENAME" is the indirect file that is beyond the exceeded limit. HP Search continued searching, without regard to "FILENAME". ACTION: Specify another search exclusively for the files in "FILENAME". Could not purge file FILENAME. (SRCHERR 230, FSERR nnn) CAUSE: You specified the file "FILENAME" using the LIST, SEARCHLOG, MATCHLOG, or PATTERNLOG option and indicated that any existing file of that name should be overwritten. The overwrite was unsuccessful, and the file system error was nnn. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. Option specified requires filename argument. (SRCHERR 250) CAUSE: You specified an option that requires an associated file name, and none was found. ACTION: Provide a file name when you specify this option. Error reading block ### of index file. (SRCHERR 260, FSERR nnn) CAUSE: A call to the FREADDIR intrinsic failed. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. Error writing block ### of index file. (SRCHERR 270, FSERR nnn) CAUSE: A call to the FWRITEDIR intrinsic failed. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. Could not open file used for indexing. (SRCHERR 280, FSERR nnn) CAUSE: HP Search found files whose indexes were out-of-date and attempted to open a file to contain the names of these files. However, this file could not be opened due to file system error nnn. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. Could not stream indexing job. (SRCHERR 290, CIERR nnn) CAUSE: After finding files whose indexes were out-of-date, HP Search built a job stream to re-index them. However, the job stream could not be started due to the command interpreter error nnn. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. Could not stream indexing job. (SRCHERR 300, FSERR nnn) CAUSE: HP Search found files whose indexes were out-of-date and built a job stream to re-index them. However, the job stream could not be started due to the file system error nnn. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. Invalid indexing method ### found in FILENAME. (SRCHERR 310) CAUSE: HP Search opened the HP Search index file "FILENAME" and found that it used an unsupported indexing method. The search will continue as if an index file did not exist and an index file update job will not be streamed. ACTION: Be sure that you do not have an MPE file equation for SRCHnnn.PUB (nnn refers to the text language number) that pointed to an incorrect file. If "FILENAME" is an HP Search index file, it can be purged (subsequent searches will build a new file). Could not open indexing job file FILENAME. (SRCHERR 320) CAUSE: Job stream file "FILENAME" to update the HP Search index file could not be opened. This is probably due to a lack of available disk space. ACTION: Purge unused files and retry the command. If this error still occurs, stop using the INDEX option until disk space is made available. Could not open file for wildcard expansion. (SRCHERR 330, FSERR nnn) CAUSE: HP Search expands wildcard file name specifiers by doing a LISTF to a temporary file. HP Search received the file system error nnn when attempting to open this file after executing the LISTF command on the file. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. LISTF error expanding fileset FILESET. (SRCHERR 340, CIERR nnn) CAUSE: HP Search expands wildcard file name specifiers by doing a LISTF to a temporary file. HP Search received the command interpreter error nnn when attempting to execute the LISTF command on fileset FILESET. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. No files found in fileset FILESET. (SRCHERR 350) CAUSE: LISTF showed no files in fileset FILESET. ACTION: Check to make sure you correctly specified the desired fileset. Too many files in fileset FILESET. (SRCHERR 360) CAUSE: HP Search expands wildcard file name specifiers by executing the LISTF command to a temporary file. The FILESET contained too many files. HP Search allocates space for 65,536 file names from LISTF. ACTION: Specify another search exclusively for the files not output in this search. LISTF file system error on fileset FILESET. (SRCHERR 370, FSERR nnn) CAUSE: HP Search expands wildcard file name specifiers by executing the LISTF command to a temporary file. HP Search received the file system error nnn when attempting to execute LISTF. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. File equation error for LISTF output. (SRCHERR 380, CIERR nnn) CAUSE: HP Search equates a file for the temporary file used by LISTF. HP Search received the command interpreter error nnn when attempting to equate files. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. Unrecognized option: OPTION. (SRCHERR 390) CAUSE: HP Search found the parameter "OPTION" in the option specification portion of the command line (after the WITH keyword) that is not a valid option. ACTION: Use the MPE system command REDO to see if you properly delimited the options on the HP Search command line. Specify only HP Search options, which are listed in Chapter 3 of this guide. Filename FILENAME is too long. (SRCHERR 400) CAUSE: Requested file name "FILENAME" contains too many characters. The maximum allowed is eight characters. ACTION: Specify a file name of eight characters or fewer. No filenames and/or patterns were requested. (SRCHERR 410) CAUSE: For a search operation at least one file name and one pattern must be requested. For an index update operation at least one file name must be requested. ACTION: Specify at least one file name and one pattern to begin a search. Specify at least one file name to update the index block file. File FILENAME already exists. Could not save. (SRCHERR 420) CAUSE: The LIST, SEARCHLOG, MATCHLOG, or PATTERNLOG option output file already exists, and the REPLACE argument was not specified. This error only occurs when HP Search is run in batch mode, and a prompt to replace the file is not appropriate. ACTION: If you want to overwrite this file, specify the REPLACE argument in the option that you specified "FILENAME". Read error on file FILENAME. (SRCHERR 430, FSERR nnn) CAUSE: A read error was detected on the file "FILENAME". HP Search received the file system error number nnn. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. Write error on file FILENAME. (SRCHERR 440, FSERR nnn) CAUSE: A write error was detected on file "FILENAME". HP Search received the file system error number nnn. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. File FILENAME is full. (SRCHERR 450) CAUSE: The file "FILENAME" is full. Processing continues but the file will not have any more records written to it. ACTION: Specify a file equation for the file so it is built larger, then re-execute the command. File holding requested filenames is full. (SRCHERR 460) CAUSE: HP Search stores the file names to be searched in a temporary file as they are input to the program. The file has been filled to capacity (approximately 2,250 file names). The search continued using the names that were output to the file. Note: File name @.@.@ is only one file name in this file. ACTION: If possible, use LISTF wildcards to get more file names into the temporary HP Search file. Could not open file to store requested filenames. (SRCHERR 470, FSERR nnn) CAUSE: HP Search stores the file names to be searched in a temporary file. File system error number nnn was received when attempting to open the file. ACTION: Refer to MPE system documentation to determine the nature of error number nnn. Could not get attribute table. (SRCHERR 480) CAUSE: HP Search failed its attempt to retrieve the NLS attribute table. ACTION: This is an internal HP Search error. Please contact HP support; investigation is required. Could not get upshift table. (SRCHERR 490) CAUSE: HP Search failed its attempt to retrieve the NLS upshift table. ACTION: This is an internal HP Search error. Please contact HP support; investigation is required. Could not get downshift table. (SRCHERR 500) CAUSE: HP Search failed its attempt to retrieve the NLS downshift table. ACTION: This is an internal HP Search error. Please contact HP support; investigation is required. Unable to get data language. (SRCHERR 510) CAUSE: HP Search failed its attempt to retrieve the NLS system data language. ACTION: This is an internal HP Search error. Please contact HP support; investigation is required. Unable to construct help catalog filename. (SRCHERR 520) CAUSE: The native language intrinsic NLAPPEND failed. ACTION: This is an internal HP Search error. Please contact HP support; investigation is required. Internal NLS error, match failed. (SRCHERR 530) CAUSE: The call to NLMATCHINIT failed because of internal NLS problems. ACTION: This is an internal HP Search error. Please contact HP support; investigation is required. Unable to initial the input pattern, match failed. (SRCHERR 540) CAUSE: The call to NLMATCHINIT failed. ACTION: This is an internal HP Search error. Please contact HP support; investigation is required. Unable to read catalog message nnn:nnn. (SRCHERR 550, nnn) CAUSE: HP Search is trying to read a message from SHCAT000.PUB.SYS and it can not be found. ACTION: This is usually caused by an incompatible program file and catalog. Make sure you are running the same versions. Submit an SR if the release had the incorrect catalog. Unable to get the user interface language; default used. (SRCHERR 560, nnn) CAUSE: The system you are running on does not have NLS configured. ACTION: No action necessary. HP Search defaults to Native-3000 (English). Unable to get the default language; NATIVE-3000 used. (SRCHERR 570, nnn) CAUSE: The system you are running on does not have NLS configured. ACTION: No action necessary. HP Search defaults to Native-3000 (English). Unable to construct the message catalog filename. (SRCHERR 580, nnn) CAUSE: An error was returned from the NLAPPEND intrinsic. ACTION: This is an internal HP Search error. Please contact HP support; investigation is required. Unable to open message catalog: FILENAME. (SRCHERR 590, nnn) CAUSE: The message catalog is either missing or unaccessable to HP Search. ACTION: Make sure the file exists, make sure you have access to it, and make sure no file equations point you elsewhere. Message catalog is out-of-date. (SRCHERR 600) CAUSE: The program file (HPSEARCH) is newer than the message catalog file (SHCAT000). ACTION: Use the latest message catalog or an older version of the program file. Using the native-3000 catalog. (SRCHERR 610) CAUSE: The message catalog for your system-configured language cannot be found. SCHAT000.PUB.SYS exists, and HP Search is using it. ACTION: You need a catalog that matches the language configured for your system. For example, SHCAT001.PUB.SYS is the message catalog if your system language is 001 (American). The record length is too long for file FILENAME. Only searching first ### characters. (SRCHERR 620) CAUSE: The file's record length is longer than HP Search can process. If you are using a file with variable-length records, this message is displayed if the physical record length is too long, even if no logical record is too long. No truncation occurs if this is the case. ACTION: If searching the first ### characters of each record is not acceptable, then reduce the size of the record length. Invalid pattern or pattern too long to be processed, "PATTERN." (SRCHERR 630) CAUSE: The pattern specified is invalid. The pattern may contain a ( or [ without the matching right ) or ]. Or, a * or + character in your pattern may be preceded by an invalid repeatable character. For example, a** is invalid. ACTION: Check your pattern to make sure it is valid. Could not create the help catalog FILENAME. (SRCHERR 640) CAUSE: When HP Search was creating the help catalog filename using the NLAPPEND intrinsic, the intrinsic failed. ACTION: This is an internal HP Search error. Please contact HP support; investigation is required. %1, %2, %3, and %4 are currently not supported in pattern "PATTERN." (SRCHERR 650) CAUSE: HP Search cannot process these binary values. ACTION: Remove the binary value from your pattern.