| Error Messages |
| You specified more than seven privileges in a PRIV_CHECK event which allows a maximum of seven. Please specify seven or fewer privileges. |
| The specified username was not found in the authorized list. Please check for typing or spelling mistakes, and re-enter the command. |
| The image name you specified in the /AUTOHIT/IMAGE qualifiers already exists in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| The username you specified in the /AUTHORIZED/USER qualifier already exists in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| The keyword you specified for /DAY is invalid. This may indicate an internal error in HITMAN. Please call Saiga Systems. |
| The free blocks text you entered was too long to contain a valid number of blocks. Please omit leading blanks and re-enter the command. |
| The operator class text you entered was too long to contain a valid operator class. Please omit leading blanks, check for typing or spelling mistakes, and re-enter the command. |
| The last command entered was requesting action from the detached process. The detached process was in the middle of a data collection and therefore the command was ignored. Please re-enter the command. |
| The event description text you entered was too long. Please omit leading blanks, check for typing or spelling mistakes, and re-enter the command. |
| You have issued a /DUMP/USER command and the HITMAN detached process is not running. Start HITMAN and re-issue the /DUMP/USER command. |
| A device name is required when entering a Check_free or Error event. Please check for typing or spelling mistakes, and re-enter the command. |
| The device name you entered was too long. Please omit leading blanks, check for typing or spelling mistakes, and re-enter the command. |
| The distribution list text you entered is too long. Please check for typing or spelling mistakes, and re-enter the command. |
| There has been an error centring text in the SMG display. Check if you have entered a string greater than 78 characters. |
| An error occurred while closing the listing file. The error message that follows will further explain the problem. |
| An error occurred while closing the log file. The error message that follows will further explain the problem. |
| An error occurred while closing the temporary mail message file. The error message that follows will further explain the problem. |
| An error occurred while closing the permanent data file. The error message that follows will further explain the problem. |
| An error occurred while reading the log file. The error message that follows will further explain the problem. |
| An error occurred while opening the audit file. The error message that follows will further explain the problem. |
| An error occurred while opening the output file for the dump command. The error message that follows will further explain the problem. |
| An error occurred while opening the listing file. The error message that follows will further explain the problem. |
| An error occurred while opening the log file. The error message that follows will further explain the problem. |
| An error occurred while opening the temporary mail message file. The error message that follows will further explain the problem. |
| An error occurred while opening the permanent data file. The error message that follows will further explain the problem. |
| An error occurred while reading from the permanent data file. The error message that follows will further explain the problem. |
| An error occurred while creating the mailbox link to the detached process. The error message that follows will further explain the problem. |
| An error occurred while starting the detached process. Please check HITMAN_DAT:HITMAN_ERROR.node_name for error messages. |
| An error occurred while writing to the listing file. The error message that follows will further explain the problem. |
| An error occurred while writing to the log file. The error message that follows will further explain the problem. |
| An error occurred while writing the temporary mail message. The error message that follows will further explain the problem. |
| An error occurred while writing to the permanent data file. The error message that follows will further explain the problem. |
| The image name you specified is already in the exit list. Please check the name and re-enter the command. |
| The image name you specified contained more than an image name. Only the file name was used. No action necessary. |
| The file name you specified was too long. Filename was truncated to 50 characters. No action necessary. |
| The first warn time must be less than the wait time. Please check for typing or spelling mistakes, and re-enter the command. |
| A file you specified does not exist. Please check for typing or spelling mistakes, and re-enter the command. |
| The number of free blocks is required when entering a check free event. Please check for typing or spelling mistakes, and re-enter the command. |
| Please specify the start or end time in the format HH:MM. There must be at least four characters. Here are some examples: "5:00" or "17:30". |
| The date you tried to add to the holiday list is already in the list. Please check for typing or spelling mistakes, and re-enter the command. |
| The date you tried to remove from the holiday list is not in the list. Please check for typing or spelling mistakes, and re-enter the command. |
| The date text you specified is too long to be a valid date. Please omit leading blanks, check for typing or spelling mistakes, and re-enter the command. |
| The identifier you specified using the /PROTECT/IDENTIFIER qualifiers already exists in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| The identifier you specified using the /PROTECT/IDENTIFIER qualifiers does not exist in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| The UIC identifier that you have entered is invalid. Please check for typing or spelling mistakes, and re-enter the command. |
| The identifier you specified using the /PROTECT/IDENTIFIER qualifiers is a UIC. Use the /UIC qualifier rather than the /IDENTIFIER qualifier. Please check for typing or spelling mistakes, and re-enter the command. |
| The image you specified using the /DISCONNECT/NOIMAGE qualifiers does not exist in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| The user you specified using the /SET_IDLE/NOUSER qualifiers does not exist in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| The maximum idle time you specified using the /MAX_IDLE qualifier is too high. Please check for typing mistakes, and re-enter the command. |
| The minimum idle time you specified using the /MIN_IDLE qualifier is too low. Please check for typing mistakes, and re-enter the command. |
| The image you specified already has wait and warning times defined. Please check for typing or spelling mistakes, and re-enter the command. |
| The server you specified already has wait and warning times defined. Please check for typing or spelling mistakes, and re-enter the command. |
| The terminal you specified already has wait and warning times defined. Please check for typing or spelling mistakes, and re-enter the command. |
| The user you specified already has wait and warning times defined. |
| The image name you specified using the /PROTECT/IMAGE qualifiers already exists in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| The image you specified using the /PROTECT/NOIMAGE qualifiers does not exist in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| An image name is required for the event you are trying to enter. Please enter event with a valid image name. |
| The image name you specified using the /DISCONNECT/IMAGE qualifiers already exists in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| The image name you specified was too long. Image name truncated to 39 characters. Please check for typing or spelling mistakes, and re-enter. |
| The image name you specified in the /AUTOHIT/NOIMAGE qualifiers does not exist in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| The image name you specified for the image threshold list already exists in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| The username you specified in the /NOUSER qualifier does not exist in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| You must specify either IN or OUT for this event. Please add the required text and re-enter the command. |
| You have entered an invalid value for the runaway buffered I/O threshold. Please check for typing mistakes, and re-enter the command. |
| You have entered an invalid value for the runaway CPU threshold. Please check for typing mistakes, and re-enter the command. |
| You have entered an invalid value for the runaway direct I/O threshold. Please check for typing mistakes, and re-enter the command. |
| You have entered an invalid disk device. Please check for typing or spelling mistakes, and re-enter the command. |
| You have tried to enter an invalid event type. Please check for typing or spelling mistakes, and re-enter the command. |
| The time specified for the first warning must be a multiple of the data collection interval. Please re-enter the command. |
| The UIC group you specified was invalid. Please check for typing or spelling mistakes, and re-enter the command. |
| The interval you specified for /UPDATE_INTERVAL is not between 1 and 60. Please check for typing or spelling mistakes, and re_enter command. |
| The key you pressed is not valid with this screen. The valid keys are listed at the bottom of the screen. |
| The UIC member you specified was invalid. Please check for typing or spelling mistakes, and re-enter the command. |
| The group and/or member in a UIC contain digits other than 0-7 and is not a valid octal number. |
| The batch queue you specified was invalid. Please check for typing or spelling mistakes, and re-enter the command. |
| The time specified for the second warning must be a multiple of the data collection interval. Please re-enter the command. |
| The time you specified for prime start must be less than the prime end time. Please check for typing or spelling mistakes, and re_enter command. |
| The update interval must be equal to or greater than the data collection interval and less than or equal to 60. Please re-enter the command. |
| You have entered a value that is less than 0. Please enter a positive value or check for typing mistakes. |
| The wait time you specified must be a multiple of the interval. Please check for typing or spelling mistakes, and enter command again. |
| The warn time you specified must be a multiple of the interval. Please check for typing or spelling mistakes, and enter command again. |
| You have entered an invalid number for the number of messages. Please enter a value between 1 and 99. |
| HITMAN stopped because either the interval is less than the minimum allowable interval or the wait time is less than the minimum allowable wait times. Please respecify interval or wait times. |
| The day you entered in not valid. Please check for typing or spelling mistakes, and re-enter the command. |
| The date you entered in not valid. Please check for typing or spelling mistakes, and re-enter the command. |
| You have entered a wildcard with a UIC identifier. Please re-enter the command without wildcard or check for typing or spelling mistakes. |
| The maximum or minimum idle limits you specified are not valid. Please check for typing mistakes, and re-enter the command. |
| The BIO threshold you specified is invalid. Please check command line for typing or spelling mistakes, and re-enter the command. |
| You have specified an invalid broadcast class. Check for typing or spelling mistakes, and re-enter the command. |
| The CPU threshold you specified is invalid. Please check command line for typing or spelling mistakes, and re-enter the command. |
| The device you specified is not available on this node. Please check command line for typing or spelling mistakes, and re-enter the command. |
| The DIO threshold you specified is invalid. Please check command line for typing or spelling mistakes, and re-enter the command. |
| The text you entered as a distribution list does not start with "@" or the length is equal to 1. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| The file name you entered was invalid. Please check for typing or spelling mistakes, and re-enter the command. |
| The force wait you specified is not between 5 and 60. Please check for typing or spelling mistakes, and enter command again. |
| The image name you specified was invalid. Please check for typing or spelling mistakes, and re-enter the command. |
| The value for minimum number of processes must be between 0 and 999. Please re_enter. |
| The operator class you specified is invalid. Please check command line for typing or spelling mistakes, and re-enter the command. |
| The operator class you specified is invalid. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| The base priority you specified is invalid. Please check command line for typing or spelling mistakes, and re-enter the command. |
| One of the privileges you tried to enter in the mask was invalid. Please check for typing or spelling mistakes, and re_enter. |
| The terminal you specified either contains a colon and a wildcard or does not end in a colon. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| The username you specified contains an illegal character or you specified a list when only a single username was allowed. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| The value you entered was invalid. Please check for typing or spelling mistakes, and re-enter the command. |
| The value you entered was invalid. Please check for typing or spelling mistakes, and re-enter the command. |
| The value you entered was invalid. Please check for typing or spelling mistakes, and re-enter the command. |
| There was an invalid value specified for the number of minutes. Please re-enter with a valid value. |
| The value you entered was invalid. Please check for typing or spelling mistakes, and re-enter the command. |
| The file name you specified contains illegal characters or is too long. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| You must specify prime start and end times when you specify a day to be prime. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| The time you specified is not valid. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| The server name you specified is not valid. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| The time you specified is not valid. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| You must specify a day when you specify prime start and end times. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| The state specified is not valid. Please re-enter with a valid state, |
| The time you specified is not valid. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| The time interval you specified is not valid. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| The UIC format that you entered was invalid. Please check for typing or spelling mistakes, and re-enter the command. |
| The username you specified contains illegal characters or you did not enter a username where one was required. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| You must specify a job name for this event. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| There must be a limit specified with this event. Please re-enter the event with a valid limit. |
| The log file is already closed, type /LOG to reopen it. |
| Logical HITMAN_DAT is not defined. Please check system logicals and define if necessary. |
| The message that you entered was too long. Message was truncated to 200 characters. No action necessary. |
| The minimum idle time must be less than the maximum idle time. Please check for typing mistakes, and re-enter the command. |
| You must specify a distribution list for this event. |
| You have successfully changed HITMAN's name. |
| You specified delete in the screen interface but there are no authorized users in the list. |
| You specified delete in the screen interface but there are no autohit images in the list. |
| You cannot delete default event records. You can only modify them. |
| You specified more than 15 characters for the nodename. Please check for typing or spelling and typing mistakes and re-enter the command. |
| HITMAN is unable to collect information on the device because the disk is not mounted or not available on this node. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| The event ID you specified to delete does not exist. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| You specified delete but there are no holidays in the list. |
| You specified delete but there are no users in the list. |
| You specified delete but there are no image exits in the list. |
| You specified delete but there are no images in the disconnect list. |
| The current log file is not found in the HITMAN_DAT directory. Please check HITMAN_DAT directory. |
| The HITMAN detached process had trouble starting, check console and HITMAN_ERROR.LOG for more information. |
| The nonprime data file PERM_DATA_NONPRIME.DAT does not exist in the HITMAN_DAT directory. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| You specified delete but there are no protected entries in the list. |
| You specified identifiers but you do not have a rights database. |
| The operation has been successfully completed. |
| You have not been authorized by the system manager to use the set idle function. |
| There are no users in the set idle list. |
| The identifier you specified does not exist. Please check for typing or spelling mistakes, and re-enter the command. |
| The node name you specified is unknown. Please check for typing or spelling and typing mistakes, and re-enter the command. |
| The image HITMAN_DETACHED.EXE must be run as a detached process. It cannot be run interactively. To start the detached process, use $ HITMAN/START. |
| The file HITMAN tried to use as a permanent data file is not a permanent data file. Ensure that the HITMAN logicals are properly defined. |
| The detached process for HITMAN is not running. This is an informational message. It does not represent an error. To start the process, use HITMAN/START. |
| You specified delete but there are no entries in the disconnect list. |
| You cannot specify a wildcard for this field. |
| The text you specified for the number of messages contained more than 2 characters. Please check for typing mistakes. |
| HITMAN requires some time to shut down. This should be no longer than 5 seconds. |
| HITMAN requires some time to start up. This should be no longer than 5 seconds. |
| A privilege is required for a Privilege Check event. Please check for typing or spelling mistakes, and re-enter the command. |
| The username you specified using the /PROTECT/PROCESS= qualifiers already exists in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| The username you specified using the /PROTECT/PROCESS= qualifiers does not exist in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| A process name is required for a Missing event. Please check for typing or spelling mistakes, and re-enter the command. |
| The process identification of the detached process is the number that was displayed. This is displayed as a result of the HITMAN/START command. |
| The process name you specified exceeds 15 characters. Please re-enter with fewer characters. |
| The process name you specified exceeds 15 characters. Please re-enter with fewer characters. |
| The username you specified using the /PROTECT/USER= qualifiers already exists in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| There was an error in processing the queue for the monitor queue event. Please verify the queue name. |
| The queue name you specified was too long. Queue name was truncated to 31 characters. No action necessary. |
| A queue name is required for this event. Please check for typing or spelling mistakes, and re-enter the command. |
| A record in the Permanent data file could not be understood by HITMAN. Please check HITMAN/LIST to make sure that all qualifiers are correct. |
| HITMAN requires the DETACH privilege to run. Make sure that you have the appropriate privilege and re-enter the command. |
| HITMAN requires the EXQUOTA privilege to run. Make sure that you have the appropriate privilege and re-enter the command. |
| HITMAN requires the OPER privilege to run. Make sure that you have the appropriate privilege and re-enter the command. |
| HITMAN requires the PRMMBX privilege to run. Make sure that you have the appropriate privilege and re-enter the command. |
| HITMAN requires the PSWAPM privilege to run. Make sure you have the appropriate privilege and re-enter the command. |
| HITMAN requires the SECURITY privilege to run. Make sure that you have the appropriate privilege and re-enter the command. |
| HITMAN requires the SYSNAM privilege to run. Make sure that you have the appropriate privilege and re-enter the command. |
| HITMAN requires the SYSPRV privilege to run. Make sure that you have the appropriate privilege and re-enter the command. |
| HITMAN requires the WORLD privilege to run. Make sure that you have the appropriate privilege and re-enter the command. |
| This informational message indicates that the HITMAN events have been resequenced. |
| You cannot use right and left arrows at this point. |
| You specified HITMAN/START, and the detached process was already running. |
| The second warning time must be less than the wait time. Please check for typing mistakes, and re-enter the command. |
| You have tried to enter a duplicate server name. Please check for typing or spelling mistakes, and re_enter. |
| A server ID that you tried to remove from the list does not exist. Please check for typing or spelling mistakes, and re_enter. |
| The server name you specified was too long. Server name was truncated to 256 characters. Please check for typing or spelling mistakes, and re-enter the command. |
| The username you specified already exists in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| You have entered an event which requires a STATE. Please re-enter the event with a valid STATE. |
| This message informs you that HITMAN was asked to shut down during a data collection. No action is required as the message is informational purposes. |
| You specified a job to be submitted as an event action but the file does not exist. |
| The terminal you specified using the /PROTECT/TERMINAL qualifiers already exists in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| A terminal name is required for this event. Please check for typing or spelling mistakes, and re-enter the command. |
| The terminal name you specified was too long. Terminal name truncated to 7 characters. Please check for typing or spelling mistakes, and re-enter the command. |
| The terminal you specified in the /PROTECT/NOTERMINAL qualifiers does not exist in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| The text you specified was too long. Please check for typing or spelling mistakes, and re-enter the command. |
| The time you specified was too long. Please check for typing or spelling mistakes, and re-enter the command. |
| More than the maximum number of authorized users were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer users. |
| More than the maximum number of autohit images were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer images. |
| More than the maximum number of events were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer events. |
| More than the maximum number of holidays were specified. Maximum number is the parameter MAX_HOLIDAYS, currently 30. Please specify fewer holidays. |
| More than the maximum number of protected identifiers were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer identifiers. |
| More than the maximum number of images were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer images. |
| More than the maximum number of set idle users were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer users. |
| More than the maximum number of protected images were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer images. |
| More than the maximum number of protected images were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer images. |
| More than the maximum number of users were specified with the qualifier /USER. Maximum number is the parameter MAX_INDIV_LEN, currently 256. Please specify fewer individuals. |
| You specified more than seven privileges in a PRIV_CHECK event which allows a maximum of seven. Please specify seven or fewer privileges. |
| More than the maximum number of processes were specified with the qualifier /PROCESS. Maximum number is the parameter MAX_INDIV_LEN, currently 256. Please specify fewer processes. |
| Your SYSGEN parameter, MAXPROCESSCNT, is greater than 1000 and HITMAN only handles 1000 processes. Please call Saiga Systems and we can customize HITMAN to suit your needs. |
| More than the maximum number of protected users were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer users. |
| More than the maximum number of runaway processes were specified. Maximum number is the parameter MAX_LIST_LEN, currently 8. Please specify fewer runaway processes. |
| More than the maximum number of servers were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer servers. |
| More than the maximum number of set idle users were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer users. |
| More than the maximum number of users were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer users. |
| More than the maximum number of terminals were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer terminals. |
| More than the maximum number of users were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer users. |
| More than the maximum number of UICs were specified. Maximum number is the parameter MAX_LIST_LEN, currently 256. Please specify fewer UICs. |
| You have tried to enter an event without the TYPE qualifier. Please re_enter the event with this qualifier. |
| The user you specified using the /DISCONNECT/USER qualifiers does not exist in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| The UIC you specified using the /PROTECT/UIC qualifiers already exists in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| The UIC that you specified in the /NOUIC qualifier does not exist in the permanent data file. Please check for typing or spelling mistakes, and re-enter the command. |
| HITMAN has tried to read a permanent data file for which it cannot establish the version. If you have just installed a new version of HITMAN, you need to convert your permanent data file to the current version. Please refer to the section on conversions programs in this manual. |
| The update interval you entered was not a multiple of the dat |