2512-001 Cannot chdir to directory_type directory, directory_name on hostname. uid=uid errno=error number.
Explanation: The chdir system call failed for the specified directory.
User Response: Check that the directory exist and the user has permission to access the directory.
2512-002 Cannot open file filename in mode mode name. errno=error_num error_msg.
Explanation: The open system call failed for the specified file.
User Response: Check that the directory and file exist and the user has permission to access the directory and the file.
2512-003 Cannot create the directory_type directory, directory_name, on hostname. uid=uid errno=error_num error_msg.
Explanation: The mkdir system call failed for the specified directory.
User Response: Check that the directory does not already exist and that the specified user has permission to create the directory.
2512-004 Cannot create pipe for program_name. errno=error_num error_msg.
Explanation: The pipe system call failed.
User Response: Correct the problem indicated by the error number.
2512-005 Open failed for file filename, errno = error_number
Explanation: The open system call failed for the specified file.
User Response: Check that the directory and file exist and the user has permission to access the directory and the file.
2512-006 Cannot continue.
Explanation: A error occurred while running the specified command and the command was unable to recover.
User Response: Retry the command. If the problem persists, contact IBM service.
2512-007 LOADL_ADMIN not specified in configuration file!
Explanation: List of one or more LoadLeveler administrators does not exist in LoadL_config file.
User Response: Add a LOADL_ADMIN entry to LoadL_config containing one or more administrator userids.
2512-010 Unable to allocate memory.
Explanation: The program could not allocate virtual memory.
User Response: Verify that the machine has a reasonable amount of vitual memory available for the LoadLeveler processes. If problem persists, contact IBM service.
2512-016 Unable to write file filename.
Explanation: A system call to write to the specified file failed.
User Response: Check that the file has write permissions and the file system is not full.
2512-017 Command transmission to LoadL_schedd on host hostname failed.
Explanation: The command was unable to contact or send data to the LoadL_schedd daemon.
User Response: Check that the LoadL_schedd daemon is running on the specified host and the host can be accessed on the network.
2512-019 Job ids must not be specified when host or user names are also specified.
Explanation: You cannot specify job ids with host or user names.
User Response: Specify either a job list or a host/user list to the command.
2512-021 Cannot connect to LoadL_schedd on host hostname.
Explanation: The command was unable to contact the LoadL_schedd daemon.
User Response: Check that the LoadL_schedd daemon is running on the specified host and the host can be accessed on the network.
2512-023 Could not obtain configuration data.
Explanation: The command was unable to open or read the LoadLeveler configuration files.
User Response: Check that all configuration and admin files exist and the user has access to the files.
2512-024 Error occurred getting cluster hostnames.
Explanation: The specified command was unable to obtain the list of hosts in the LoadLeveler cluster. The failure may be due to an error opening or reading the LoadLeveler configuration files or a syntax error in one of the configuration files.
User Response: Check that all configuration and admin files exist and the user has access to the files. Retry the command. If the problem persists, contact IBM service.
2512-025 Only the LoadLeveler administrator is permitted to issue this command.
Explanation: The specified command must be issued by a LoadLeveler administrator. The user issuing the command is not listed as an administrator in the LoadLeveler configuration file.
User Response: Add the user to the LOADL_ADMIN list in the config file or have an administrator issue the command.
2512-027 Dynamic load of filename from system_name failed. errno=error_num error_msg.
Explanation: The load system call failed for the specified file.
User Response: Check that the specified file has been installed in the specified directory and has the correct permissions.
028 ERROR 2512-028 ERROR error at line line_num in file filename.
Explanation: A LoadLeveler daemon or command detected internal data corruption and terminated.
User Response: If problem persists, contact IBM service.
2512-029 Cannot establish UNIX domain listen socket for path, pathname. errno=error num error msg
Explanation: The listen system call failed. A LoadLeveler process was attempting to listen on a UNIX domain socket to communicate with another process.
User Response: Correct the problem indicated by the error number.
2512-030 Cannot stat file filename.
Explanation: stat() returned a failure code for named file. The stat system call failed for the specified file.
User Response: Check that the file exists and has adequate permissions.
2512-031 Cannot change mode on file filename to file permissions.
Explanation: The chmod system call failed attempting to change permissions on the specified file.
User Response: Check that the file exists and has adequate permissions.
2512-032 Cannot open file filename. errno = error num
Explanation: The open system call failed for the specified file.
User Response: Check that the directory and file exist and the user has permission to access the directory and the file.
2512-033 Cannot open file filename.
Explanation: The open system call failed for the specified file.
User Response: Check that the directory and file exist and the user has permission to access the directory and the file.
2512-051 This job has not been submitted to LoadLeveler.
Explanation: The job was not submitted because of an error. This message is preceeded by a message explaining the error.
User Response: Correct the error indicated in the previous message.
2512-052 Submit Filter: rc = return_code.
Explanation: The submit filter returned a non-zero exit code. The job was not submitted.
User Response: Contact the LoadLeveler administrator who provided the submit filter to determine the cause of the problem.
2512-053 Unable to process the job command file (filename) from the Submit Filter filter.
Explanation: The stat system call failed for the filtered job command file.
User Response: Contact the LoadLeveler administrator who provided the submit filter to determine the cause of the problem.
2512-054 Unable to process the job command file (filename) from the Submit Filter filter. No output.
Explanation: The submit filter returned an empty job command file.
User Response: Contact the LoadLeveler administrator who provided the submit filter to determine the cause of the problem.
2512-055 Unable to process the job command file filename for input, the error is: error.
Explanation: This message is the result of either a failure opening the job command file or an error running the submit filter.
User Response: Check that the job command file exists and the user has permission to access the directory and the file. If a submit filter is configured, contact LoadLeveler administrator who provided the submit filter to determine the cause of the problem.
2512-056 Unable to process the job command file filename .
Explanation: This message is the result of either a failure opening the job command file or an error running the submit filter.
User Response: Check that the job command file exists and the user has permission to access the directory and the file. If a submit filter is configured, contact LoadLeveler administrator who provided the submit filter to determine the cause of the problem.
2512-057 Unable to process the contents of the job command file filename .
Explanation: The job command file does not contain any LoadLeveler commands. A LoadLeveler command or keyword statement must be proceeded by #@ and no statements are in the file.
User Response: Correct the command file as required to correctly identify LoadLeveler commands and resubmit the job.
2512-058 The command file filename does not contain any queue keywords.
Explanation: The job command file does not contain a LoadLeveler "queue" keyword. At least one queue keyword is required in a LoadLeveler job.
User Response: Correct the command file and resubmit the job.
2512-059 Unable to process the command file filename . The syntax is unknown.
Explanation: The job command file does not contain any valid LoadLeveler statements.
User Response: Correct the job command file and resubmit the job.
2512-060 Syntax error: keyword unknown command file keyword.
Explanation: The specified keyword is not a valid LoadLeveler keyword.
User Response: Correct the job command file and resubmit the job.
2512-061 Syntax error: keyword = keyword_value unknown keyword value.
Explanation: The specified value is not valid for this keyword.
User Response: Correct the job command file and resubmit the job.
2512-062 Syntax error: keyword = keyword_value takes only one keyword value.
Explanation: More than one value was given for the specified keyword which accepts only one value.
User Response: Correct the command file and resubmit the job.
2512-063 Syntax error: keyword = num_value is not a valid numerical keyword value.
Explanation: The value given for the specified keyword is not a numeric value. This keyword requires a numeric value.
User Response: Correct the command file and resubmit the job.
2512-064 Syntax error: keyword = keyword_value keyword value must be greater then zero.
Explanation: The value given for the specified keyword is not a positive number. This keyword requires a numeric value greater than zero.
User Response: Correct the job command file and resubmit the job.
2512-065 Unable to expand job command keyword keyword = keyword_value .
Explanation: The keyword cannot be expanded using the job command file macros.
User Response: Correct the command file and resubmit the job.
2512-066 Unable to expand job command keyword value keyword = keyword_value .
Explanation: The specified macro used as a keyword value could not be expanded.
User Response: Check that the macro is correctly defined in the job command file and resubmit the job.
2512-067 The keyword statement cannot exceed number characters.
Explanation: The keyword statement including all substitutions and expansions cannot exceed the specified length.
User Response: Correct the job command file and resubmit the job.
2512-068 The specified job_name of keyword is not valid.
Explanation: The value of the "job_name" keyword statement is not valid. The job name can contain alphamuermic characters.
User Response: Correct the command file and resubmit the job.
2512-069 The specified step_name of command_file is not valid.
Explanation: The value of the "step_name" keyword statement is not valid. The step name must a) start with an alphabetic character b) contain only alphanumeric characters and c) cannot be either T or F.
User Response: Correct the job command file and resubmit the job.
2512-070 Invalid character(s) were specified for notify_user = user_name .
Explanation: The |, <, >, or ; characters are not allowed in the name of the notify user.
User Response: Correct the job command file and resubmit the job.
2512-074 The priority value is not valid: keyword = keyword_value .
Explanation: The priority value must be between 0 and 100.
User Response: Correct the job command file and resubmit the job.
2512-076 The required keyword keyword was not found in the administration file.
Explanation: An error occurred while processing the LoadLeveler administration file.
User Response: Resubmit the job. If problem persists, contact IBM service.
2512-077 A valid class could not be found in the default class list.
Explanation: The resource limits specified for the job exceed the resource limits for all classes in the default_class list specified for this user.
User Response: Take one of the following actions: specify a class in the job command file that satisfies the job's resource limits; adjust the resource limits specified in the job command file; have the LoadLeveler administrator add a class capable of accepting the job to the default_class list for the user.
2512-078 Group group_name is not valid for user user_name .
Explanation: The group assigned to this job either excludes or does not include the user.
User Response: Take one of the following actions: specify a valid group for the user in the job command file; have the LoadLeveler administrator allow the user in the specified group; have the LoadLeveler administrator change the default group for the user.
2512-079 Class classname is not valid for user user_name .
Explanation: The class assigned to this job either excludes or does not include the user.
User Response: Take one of the following actions: specify a valid class for the user in the job command file; have the LoadLeveler administrator allow the user to use the specified class; have the LoadLeveler administrator change the default class for the user.
2512-080 Class classname is not valid for group group_name .
Explanation: The class assigned to this job either excludes or does not include the group.
User Response: Take one of the following actions: specify a valid class for the group or a valid group for the class in the job command file; have the LoadLeveler administrator allow the group to use the specified class; have the LoadLeveler administrator change the default class or default group for the user.
2512-081 Account number num is not valid for user user_name .
Explanation: The account validation program determined that this user is not permitted to use the account number specified in the job command file.
User Response: If the default account validation program is being used then either use an account number assigned to the user or have the LoadLeveler administator add the account number to the user stanza in the administration file. If an installation specific account validation program is being used then contact the LoadLeveler administrator.
2512-082 Condition code specified in the statement dependency = condition_code is not valid.
Explanation: The condition code in the dependency statement must be CC_NOTRUN, CC_REMOVED, or an integer value within the range of 0 and 255.
User Response: Correct the job command file and resubmit the job.
2512-083 The condition code integer value specified in the statement dependency = value is not within the range of 0 and 255.
Explanation: The condition code in the dependency statement must be CC_NOTRUN, CC_REMOVED, or an integer value within the range of 0 and 255.
User Response: Correct the job command file and resubmit the job.
2512-084 The expression specified in the statement dependency = dependency_value is not valid.
Explanation: The value for the dependency statement must contain one or more expressions of the form . Multiple expressions must be separated by logical operators && or ||.
User Response: Correct the job command file and resubmit the job.
2512-085 The syntax in the statement dependency = dependency_value is not valid.
Explanation: The value for the dependency statement must contain one or more expressions of the form . Mutiple expressions must be separated by logical operators && or ||.
User Response: Correct the job command file and resubmit the job.
2512-086 The step_name in the statement dependency = dependency_value is not valid.
Explanation: The step name in the dependency statement is not valid. The step name must a) start with an alphabetic character b) contain only alphanumeric characters and c) cannot be either T or F.
User Response: Correct the job command file and resubmit the job.
2512-087 The step_name in the statement dependency = dependency_value was not previously defined.
Explanation: Any step_name used in the dependency statement must be the name of a previously defined job step.
User Response: Correct the job command file and resubmit the job.
2512-088 The operator in the statement dependency = dependency_value is not valid.
Explanation: The value for the dependency statement must contain one or more expressions of the form . Mutiple expressions must be separated by logical operators && or ||.
User Response: Correct the job command file and resubmit the job.
2512-089 Syntax error: Class should not be included as part of keyword_value .
Explanation: The class keyword cannot be used in a requirements or preferences statement.
User Response: Correct the job command file and resubmit the job.
2512-090 The getcwd function failed with error error_num.
Explanation: The command was unable to determine the current working directory. The default for the "initialdir" keyword is the current working directory.
User Response: Correct the command file and resubmit the job.
2512-095 The resource limit resource_identification is unknown.
Explanation: The command detected internal data corruption and terminated.
User Response: If the problem persists contact IBM service.
2512-096 This non-AIX version of LoadLeveler does not support check pointing.
Explanation: Check pointing is only supported on AIX versions of LoadLeveler.
User Response: Correct the job command file and resubmit the job.
2512-097 This non-AIX version of LoadLeveler does not support parallel job.
Explanation: Parallel jobs are only supported on AIX versions of LoadLeveler.
User Response: Correct the job command file and resubmit the job.
2512-098 This non-AIX version of LoadLeveler does not support PVM3 jobs.
Explanation: PVM3 jobs are only supported on AIX versions of LoadLeveler.
User Response: Correct the job command file and resubmit the job.
2512-101 The executable's version of the check pointing library can not be determined.
Explanation: Check pointing requires that the executable be linked with the check pointing library.
User Response: Link edit the executable with the correct version of the check pointing library and resubmit the job.
2512-102 The CkptVersion cannot be defined in the requirements keyword statement.
Explanation: CkptVersion cannot be explicity specified in the requirements statement. If checkpointing is requested in the job command file then CkptVersion is implicitly added to the requirements statement by LoadLeveler.
User Response: Remove the CkptVersion expression from the requirements statement and resubmit the job.
2512-105 The keyword_value conflicts with the Adapter = in the requirements or preferences statements.
Explanation: A job command file cannot contain both a network statements and an adapter keyword in the requirements statement.
User Response: The network statement is the preferred method for requesting adapters. Remove the adapter expression from the requirements statement and resubmit the job.
2512-108 Syntax error: node = keyword_value minimum is greater than maximum.
Explanation: The minium number of nodes must be less than or equal to the maximum number of nodes.
User Response: Correct the job command file and resubmit the job.
2512-109 The keyword LoadLeveler keyword is not valid for an NQS job:
Explanation: The specified keyword is not allowed in a job command file for a job that is to be routed to NQS. The supported level of NQS does not have an option equivalent to this keyword.
User Response: Correct the job command file and resubmit the job.
2512-110 The NQS_submit keyword must be specified for class class_name .
Explanation: The specified class has "NQS_class=true" but the class does not have the NQS_submit keyword which specifies the NQS queue for job submission.
User Response: Have the LoadLeveler administrator correct the administration file and resubmit the job.
2512-111 The NQS_query keyword must be specified for class class_name .
Explanation: The specified class has "NQS_class=true" but the class does not have the NQS_query keyword which specifies the NQS queue for job monitoring.
User Response: Have the LoadLeveler administrator correct the administration file and resubmit the job.
2512-112 The NQS keyword keyword_value is missing a required value.
Explanation: The NQS keyword requires a value.
User Response: Correct the job command file and resubmit the job.
2512-114 Unable to allocate number bytes of memory using malloc().
Explanation: The program could not allocate virtual memory.
User Response: Verify that the machine has a reasonable amount of vitual memory available for the LoadLeveler processes. If problem persists, contact IBM service.
2512-115 Unable to connect to a schedd machine.
Explanation: The submit command was unable to connect to a LoadLeveler schedd machine.
User Response: Check that a LoadL_schedd daemon is running on this machine or on at least one public scheduling machine. Check that the scheduling machine can be accessed on the network.
2512-116 Unable to submit a job to the schedd machine.
Explanation: The submit command was either unable to connect or send the job data to a LoadLeveler schedd daemon.
User Response: Check that a LoadL_schedd daemon is running on this machine or on at least one public scheduling machine. Check that the scheduling machine can be accessed on the network.
2512-117 This check pointing job requires the CHKPT_FILE or CHKPT_DIR environment variables.
Explanation: A parallel LoadLeveler job with user initiated check pointing requires the CHKPT_FILE or CHKPT_DIR environment variables to be set.
User Response: Set either variable and resubmit the job command file.
2512-118 A job_type = parallel with checkpoint = system_initiated is not valid.
Explanation: A parallel LoadLeveler job may not use system initiated check pointing.
User Response: Correct the job command file and resubmit the job command file.
2512-119 Root cannot run a LoadLeveler job.
Explanation: The root user (id = 0 ) is not allowed to submit a job command file to LoadLeveler.
User Response: Logon as a different user and resubmit the job command file.
2512-120 The directory directory_name does not exist.
Explanation: The specified directory either does not exist, is not accessible by the user, or is not a directory.
User Response: Create the directory with the proper access persmissions or change the directory specified in the job command file and resubmit the job.
2512-121 Syntax error: keyword = keyword_value invalid keyword value or it cannot be evaluated.
Explanation: The value of the keyword contains a macro that cannot be evaluated or is not a valid date.
User Response: Correct the job command file and resubmit the job.
2512-122 Unable to get passwd entry for uid user_uid
Explanation: The system call getpwuid failed for the specified uid.
User Response: Check that the user has read access to the /etc/passwd file and there is an entry in /etc/passwd for the specified user.
2512-123 The command was unable to set the built in macros.
Explanation: A failure occurred during macro processing. This message is preceded by a message describing the cause of the failure.
User Response: Correct the problem indicated by the preceding message.
2512-124 Duplicate step names step_names are not allowed.
Explanation: The step names in the job command file must be unique.
User Response: Correct the job command file and resubmit the job.
2512-125 Unable to convert keyword = keyword_value to a valid date/time format.
Explanation: The value of the specified keyword is not a valid date/time.
User Response: Correct the date/time value in the job command file and resubmit the job.
2512-126 Syntax error: The keyword keyword is required in the job command file.
Explanation: This job type or job command file requires the specified keyword.
User Response: Correct the job command file and resubmit the job.
2512-127 Unable to calculate the image size. The keyword keyword is in error.
Explanation: The specified keyword was not found in the job command file.
User Response: Correct the job command file and resubmit the job.
2512-128 Unable to obtain the request name to build the standard output filename.
Explanation: The submit command detected internal data corruption of the job name.
User Response: If problem persists, contact IBM service.
2512-129 The NQS keywords keyword1 and keyword2 are in conflict.
Explanation: Two of the NQS keywords are in conflict with each other.
User Response: Correct the job command file and resubmit the job.
2512-130 The keyword is required in the configuration file.
Explanation: The submit command detected internal data corruption of the configuration data.
User Response: If problem persists, contact IBM service.
2512-132 The step_name step_name in the requirements statement is not being referenced in the dependency statement.
Explanation: A requirements statements refers to a machine on which another step will run. In order to evaluate the requirements statement, the referenced step must run prior to the referencing step. A dependency statement is necessary to insure the steps are run in the proper order.
User Response: Add a dependency statement to the referencing step.
2512-133 The machine.stepname cannot be specified for parallel type job step.
Explanation: The machine.stepname cannot be specified in the requirements statements for a parallel type job step.
User Response: Correct the job command file and resubmit the job.
2512-134 The keyword_value network_type or adapter_name are not defined in an adapter stanza.
Explanation: A network statement or an adapter requirement referenceda network_type or adapter_name that was not found in the administration file
User Response: Either change the network_type/adapter_name in the job command file or have the LoadLeveler administration define the network_type/adapter_name in the administration file.
2512-135 For the keyword keyword, maximum number of nodes requested is greater than allowed for this stanza_name .
Explanation: The requested maximum number of nodes exceeds the maximum allowed by the specified administration stanza.
User Response: Either reduce the maximum number of nodes in the job command file or have the LoadLeveler administrator increase the number allowed.
2512-136 For the stanza_name keyword, the total number of tasks requested is greater than allowed for this keyword .
Explanation: The requested total tasks exceeds the maximum allowed by the specified administration stanza.
User Response: Either reduce the total number of tasks in the job command file or have the LoadLeveler administrator increase the number allowed.
2512-137 The number of request_nodes requested nodes exceeds the number of requested_tasks requested tasks.
Explanation: The requested number of nodes is greater than the requested total tasks.
User Response: Correct the job command file and resubmit the job.
2512-138 Syntax error: the keyword1 and keyword2 keywords are not allowed in the same step.
Explanation: Both of these keywords are not allowed in the same job step.
User Response: Correct the command file and resubmit the job.
2512-139 The keyword keyword is not valid for job_type = pvm3 job steps.
Explanation: This keyword is not valid when the job type is pvm3.
User Response: Correct the command file and resubmit the job.
2512-140 The keyword keyword is only valid for job_type = pvm3 job steps.
Explanation: This keyword is only valid when the job type is pvm3.
User Response: Correct the command file and resubmit the job.
2512-141 Syntax error: Multiple "keyword value" keywords are not allowed in a "keyword type" statement.
Explanation: Only one keyword type is allowed in the keyword statement.
User Response: Correct the command file and resubmit the job.
2512-142 Syntax error: Invalid Adapter operation in a keyword type statement.
Explanation: Only the Adapter = = is allowed in the keyword statement.
User Response: Correct the command file and resubmit the job.
2512-143 Syntax error: Invalid adapter name in a keyword type statement.
Explanation: The adapter name in the Adapter keyword is not valid.
User Response: Correct the command file and resubmit the job.
2512-144 The keyword keyword is not valid when the node keyword contains minimum and maximum values which are not equal to each other.
Explanation: This keyword is not valid when a minimum and maximum value specified on the node keyword are not equal to each other.
User Response: Correct the command file and resubmit the job.
2512-145 The keyword keyword is not compatable with min_processors and/or max_processors.
Explanation: The keywords (min_processor and/or max_processor) can not be used within the same job step that specifies the node keyword.
User Response: Correct the command file and resubmit the job.
2512-146 The keyword keyword is not valid for job_type = serial job steps.
Explanation: This keyword is not valid when the job type is serial.
User Response: Correct the command file and resubmit the job.
2512-150 Not enough available filesystem space for transfer_data. Transfer from host aborted.
Explanation: Not enough available filesystem space to write transferred data.
User Response: Check statvfs() man pages for possible causes of failure.
2512-151 Error receiving history file from host.
Explanation: An error occurred during the file transfer.
User Response: Check communication paths to that host.
2512-152 GLOBAL_HISTORY is not specified in config file.
Explanation: GLOBAL_HISTORY directory does not exist in LoadL_config file and none was specified as a command line parameter to llacctmrg.
User Response: Add the directory where the global history file is to be copied in the GLOBAL_HISTORY entry of LoadL_config or specify the directory as a command parameter to llacctmrg.
2512-282 A userlist, hostlist or joblist must be specified.
Explanation: Data missing.
User Response: Specify a userlist, hostlist or joblist with llcancel.
2512-176 Internal errors detected. Exiting.
Explanation: This command has detected serious internal errors and can not continue.
User Response: Make sure that LoadLeveler is running and correctly configured.
2512-177 Unable to obtain machine status information from the central manager.
Explanation: Unable to obtain information about machines in the LoadLeveler cluster from the central manager.
User Response: Check to see if the central manager host is up and if the LoadL_negotiator is running on it.
2512-178 No class information is available in the LoadLeveler administration file.
Explanation: No class information found in the LoadLeveler administration file.
User Response: Make sure that LoadLeveler is running and correctly configured.
2512-181 No machinelist specified for purge. Command was not sent.
Explanation: No machine names were passed to the purge command.
User Response: Reissue the command with the name of the LoadL_schedd hosts you wish to purge.
2512-182 The keyword keyword is not valid.
Explanation: An invalid keyword was specified for llctl.
User Response: Refer to usage information for a list of valid keywords.
2512-183 Error occurred sending command_name command to hostname.
Explanation: Error occurred sending the command to specified host.
User Response: Check to see if the intended host is available over the network and that LoadLeveler is running. Contact a LoadLeveler administrator if necessary.
2512-184 Unknown class class_name specified in classlist.
Explanation: A class name was specified with either the drain or resume keywords that does not exist with the LL configuration.
User Response: Reissue the command with a valid class name.
2512-185 No event name specified for capture. Command was not sent.
Explanation: No event name was passed to the capture command.
User Response: Reissue the command with the name to be used to capture the event.
2512-187 Cannot evaluate StartdAvail state.
Explanation: Cannot determine if a LoadL_startd is in "Drain" state.
User Response: Check command and make sure that a valid host list was passed.
2512-188 Error allocating machine object for machine name.
Explanation: Cannot allocate an object corresponding to the named machine.
User Response: Check command and make sure that a nameserver-resolvable host name was passed.
2512-199 illegal option is an unrecognized option.
Explanation: An unrecognized option was specified.
User Response: Re-issue the command, specifying only valid options.
2512-200 Errors encountered, processing halted.
Explanation: Errors were encountered while processing command line.
User Response: Correct the errors reported and re-issue the command.
2512-201 Unable to open the files file1, file2.
Explanation: lldbconvert is either not being run in the local spool directory, or the user running the program has insufficient permissions to write in the local spool directory. Cannot open the specified files.
User Response: Check path and permissions.
2512-202 Unable to convert job job number, job name. Previous messages may indicate cause.
Explanation: Unable to convert job step from old format to new format.
User Response: Make a note of the job number. Earlier messages may indicate the reason for the failure.
2512-203 Unable to store job job number, job name in queue file names files.
Explanation: Unable to store job number.
User Response: Check available disk space in local spool directory's file system. Check permissions on spool directory and files.
2512-204 Cannot rename file name file1 to file2.Error (error number) was: error message.
Explanation: Cannot rename the file from string1 to string2.
User Response: Use the information in the error explanation to correct the problem.
2512-205 The job_queue files to be converted are in old LoadLeveler version format, not in 1.3 format.
Explanation: Spool files are not in the expected original format or in the desired format.
User Response: lldbconvert cannot be used. Delete or rename all spool files before bringing up the new version of LoadLeveler.
2512-206 function failed for job = job_num , step = job_step_num.
Explanation: Failed to fetche job at the XDR level.
User Response: Make note of the job number. lldbconvert will discard an entire job if it fails to convert one of its job steps.
2512-207 Incorrect PROC version number (version_num). Converting to NULL PROC.
Explanation: Unknown proc version number encountered. XDR routines will pretend it is empty to avoid failure of entire transmission.
User Response: Keep track of job and job step numbers. If lldbconvert succeeds, issue "llq" after you have started the new version of LoadLeveler to see what data was lost. Also pay attention to additional error messages issued by lldbconvert.
2512-220 Favorjob command has not been sent to the central manager.
Explanation: Command not sent due to an error condition.
User Response: Check to see if the central manager host is up and if the LoadL_negotiator is running on it.
2512-225 Favoruser command has not been sent to the central manager.
Explanation: Command not sent due to an error condition.
User Response: Check to see if the central manager host is up and if the LoadL_negotiator is running on it.
2512-229 Only a LoadLeveler administrator is permitted to use the -s option of this command.
Explanation: A non-administrator is attempting to specify the -s option of this command.
User Response: Do not use the -s option unless you are a LoadLeveler administrator.
2512-230 Can not find password entry for user uid number.
Explanation: A matching entry for the uid number does not exist in the /etc/password file.
User Response: Check /etc/passwd file for corruption. This error is very unlikely to occur.
2512-231 Hold command has not been sent to the central manager.
Explanation: Command not sent since an error condition has been encountered.
User Response: Check to see if the central manager host is up and if the LoadL_negotiator is running on it.
2512-232 The format of character string specified (= LoadLeveler job or job step name) is not valid for a LoadLeveler job or job step.
Explanation: A string having the format: [hostname].job_id.[step_id] is expected.
User Response: Specify a string of the expected format.
2512-243 Priority command has not been sent to the central manager.
Explanation: Command not sent since an error condition has been encountered.
User Response: Check to see if the central manager host is up and if the LoadL_negotiator is running on it.
2512-244 Blank space is not allowed between + or - sign and priority adjustment specification.
Explanation: There should be no blank space between +/- sign and integer specification of priority adjustment.
User Response: Remove the blank space. For example, specify +30 not + 30.
2512-249 When specifying the -x option, please do not specify -h, -u or more than one job id.
Explanation: Conflicting options specified.
User Response: Refer to usage output or LoadLeveler User's Guide for usage information.
2512-250 No hostlist was specified. A hostlist is required with the -h option.
Explanation: llq -h was issued without a hostlist.
User Response: Reissue the command with a hostlist.
2512-251 No userlist was specified. A userlist is required with the -u option.
Explanation: llq -u was issued without a userlist.
User Response: Reissue the command with a userlist.
2512-253 The -u option and the -s option are incompatible.
Explanation: Conflicting options.
User Response: Reissue the llq command using either the -s or -u option but not both.
2512-255 A job list must be specified if the -s option is used.
Explanation: llq -s issued with no job ids.
User Response: Specify one or more job ids.
2512-261 The -u option can not be used when a job list has already been specified.
Explanation: The -u option of the llq command can not be used when a job list has been specified.
User Response: Do not use the -u option when a job list has been specified.
2512-262 Encountered one or more errors while processing the list of host names.
Explanation: The llq command encountered errors while processing the arguments of the -h option.
User Response: Verify that the host names associated with the -h option are valid host names.
2512-263 Encountered one or more errors while processing the list of user names.
Explanation: The llq command encountered errors while processing the arguments of the -u option.
User Response: Verify that the user names associated with the -u option are valid user names.
2512-264 The -c option and the -s option are incompatible.
Explanation: Conflicting options.
User Response: Reissue the llq command using either the -s or -c option but not both.
2512-265 No class list was specified. A class list is required with the -c option.
Explanation: llq -c was issued without a class list.
User Response: Reissue the command with a class list.
2512-266 Encountered one or more errors while processing the list of class names.
Explanation: The llq command encountered errors while processing the arguments of the -c option.
User Response: Verify that the class names associated with the -c option are valid class names.
2512-267 The -x option is not compatible with the -s, -r, or -f options.
Explanation: Conflicting options.
User Response: Reissue the llq command using only valid combinations of options.
2512-268 The -s option is not compatible with the -u, -x, -r, -f, or -c options.
Explanation: Conflicting options.
User Response: Reissue the llq command using only valid combinations of options.
2512-269 The -l option is not compatible with the -r, or -f options.
Explanation: Conflicting options.
User Response: Reissue the llq command using only valid combinations of options.
2512-270 The -r option is not compatible with the -l, -s, -x, or -f, options.
Explanation: Conflicting options.
User Response: Reissue the llq command using only valid combinations of options.
2512-271 An error was detected while processing the parameters of the -r or -f option.
Explanation: An invalid parameter of -r or -f option has been specified.
User Response: Execute llq -H to obtain a complete list of valid parameters of the -r or -f option.
2512-272 The -f option is not compatible with the -l, -s, -x, or -r options.
Explanation: Conflicting options.
User Response: Reissue the llq command using only valid combinations of options.
2512-273 A job list can be specified only once.
Explanation: More than one job list has been specified.
User Response: Reissue the llq command with only one list of job IDs.
2512-274 A job list can not be specified when a user list has also been specified.
Explanation: Conflicting options.
User Response: Reissue the llq command using only valid combinations of options.
2512-275 An error was detected while processing the list of job names.
Explanation: An invalid job name or job step name has been specified.
User Response: Reissue the llq command using valid job names or job step names.
2512-276 A long listing of schedd machine namejob ID.step ID is not available since you are not a LoadLeveler administrator or the owner of the job.
Explanation: Only a LoadLeveler administrator or owner of a job can request a long listing.
User Response: Do not use the -l or -x option of the llq command unless you are the owner of the job or a LoadLeveler administrator.
2512-277 The -h option is compatible with a job list only when the -s option is also specified.
Explanation: The -h option of the llq command can not be used with a job list unless the -s option is also specified.
User Response: Do not use -h option when a job list has been specified unless -s is specified.
2512-293 A duplicate category associated with -f or -r option has been specified.
Explanation: A sub-option of the -f or -r option was specified more than once.
User Response: Each distinct sub-option should not be specified more than once. Use the -H option to get a list of valid sub-options.
2512-294 The central manager is not defined in the LoadLeveler administration file.
Explanation: Unable to obtain information about the central manager machine.
User Response: Check to see if a central manager is defined in the LoadLeveler administration file.
2512-295 The -l, -r, -f options of this command are mutually exclusive.
Explanation: Do not specify these options in any combinations.
User Response: Specify either -l, or -r, or -f but not a combination of these options.
2512-296 An invalid category associated with -f or -r option has been specified.
Explanation: An invalid sub-option of the -f or -r option was specified.
User Response: Specify valid sub-options only. Use the -H option to get a list of valid sub-options.
2512-297 The arguments of this command contain characters not in the ASCII character set. Exiting.
Explanation: The arguments of this command contain characters not in the ASCII character set.
User Response: Specify only valid arguments.
2512-311 parameter is not a valid option for the -r flag. Valid options are: all, resource, throughput, avgthroughput, minthroughput, maxthroughput, numeric.
Explanation: The argument specified is not valid for the -r flag.
User Response: Refer to the displayed list of valid arguments.
2512-312 Missing date for -s or -e flag.
Explanation: One or more dates omitted.
User Response: Enter a date for the -s flag and the -e flag.
2512-313 The date range specified is not valid.
Explanation: Start date is later than End date.
User Response: Enter a valid date range.
2512-314 Cannot find history file.
Explanation: History file cannot be found.
User Response: Enter a history file name on the command line or specify a HISTORY file in the LoadL_config or LoadL_config.local file.
2512-315 HISTORY file path not specified in LoadL_config file.
Explanation: History file not found in LoadL_config or LoadL_config.local.
User Response: Specify a HISTORY file in the LoadL_config or LoadL_config.local file.
2512-316 Unable to malloc num bytes for work record.
Explanation: Unable to allocate memory
User Response: Free up memory on local host.
2512-317 Unable to malloc num bytes for work statistics.
Explanation: Unable to allocate memory
User Response: Free up memory on local host.
2512-318 parameter is not a valid option for the -d flag.
Explanation: the argument specified is not valid for the -d flag.
User Response: Refer to the displayed list of valid arguments.
2512-377 The SDR Class classname class does not contain any SDR objects.
Explanation: The command was unable to extract any objects from the SDR class.
User Response: Contact the system administrator to start problem determination procedures for the SDR.
2512-378 The SDR system partition does not contain any machine definitions.
Explanation: The command was unable to find SDR Node class entries for the machines in the system partition definition in the System Data Repository.
User Response: Contact the system administrator to start problem determination procedures for the SDR.
2512-379 The SDR function function_name failed with a return code of return_code.
Explanation: The command issued a function to extract data from the SDR and the SDR function failed with the specified return code.
User Response: Contact the system administrator to start problem determination procedures for the SDR.
2512-380 The SDR attribute attribute was not found in the SDR class classname object.
Explanation: The command could not find the attribute in the SDR class object.
User Response: Contact the system administrator to start problem determination procedures for the SDR.
2512-381 An SP_NAME of SP_NAME was found. Verify that this is a vaild partition.
Explanation: The command could not find the partition.
User Response: Contact the system administrator to start problem determination procedures for the SDR.
2512-426 Step step_id was marked not runnable at time due to dependency.
Explanation: Step is not runnable because dependency condition evaluated to false.
User Response:
2512-427 Step step_id has been canceled because it was rejected num time(s).
Explanation: Step was canceled.
User Response: Check that the job's requirements can be met on at least one machine in the LoadLeveler cluster and that the user ID of the submitter is valid on sufficient machines in the LoadLeveler cluster, and resubmit the job. If problem persists, contact the LoadLeveler administrator.
2512-428 Step step_id has been put on user hold because it has been rejected num time(s).
Explanation: Step was put on user hold.
User Response:
2512-429 Problem with history file.
Explanation: Report history file problem.
User Response: Retry the command. If problem persists, contact the LoadLeveler administrator.
2512-430 Error appending job job_name to the history file, errno = UNIX_error_num.
Explanation: History file problem.
User Response: Contact the LoadLeveler administrator.
2512-431 Accounting has been disabled on machine: machine_name.
Explanation: History file problem.
User Response: Contact the LoadLeveler administrator.
2512-432 Re-enable with: llctl -h hostname reconfig or llctl -h hostname recycle.
Explanation: History file problem.
User Response: If you are a LoadLeveler administrator, run llctl -h reconfig or llctl -h recycle and retry the command. If not, contact the LoadLeveler administrator.
2512-433 2512-433 has been put on system hold because it has been rejected num time(s).
Explanation: Step was put on system hold.
User Response: Check that the job's requirements can be met on at least one machine in the LoadLeveler cluster and that the user ID of the submitter is valid on sufficient machines in the LoadLeveler cluster, and resubmit the job. If problem persists, contact the LoadLeveler administrator.
2512-436 Cannot complete handshake with daemon_name at hostname.
Explanation: A process is unable to complete the protocol handshake with a LoadLeveler daemon.
User Response: Verify that the command version and daemon version are compatible.
2512-437 Can't send command to daemon_name at hostname.
Explanation: A process is unable to send a transaction (command) to a LoadLeveler daemon.
User Response: Check to see if the daemon is active. Re-issue the command.
2512-438 Can't send command parms to daemon_name at hostname.
Explanation: A process is unable to send a transaction parameters to a LoadLeveler daemon.
User Response: Check to see if the daemon is active. Re-issue the command.
2512-439 Unable to receive ack from daemon_name at hostname.
Explanation: A process is unable receive an aknowledgement from LoadLeveler daemon.
User Response: Check to see if the daemon is active. Re-issue the command.
2512-440 Unable to malloc num bytes for list.
Explanation: Unable to allocate memory
User Response: Free up memory on local host.
2512-441 Specified step name step_name is not a valid name for a LoadLeveler job.
Explanation: Self explanatory
User Response: Re-issue the command specifying a correct LoadLeveler step name.
2512-442 statvfs(filename,address) failed. Errno = error_num.
Explanation: The statvfs function call failed.
User Response: Use the errno value to determine the reason for failure.
2512-443 statfs(filename,address) failed. Errno = error_num.
Explanation: The statfs function call failed.
User Response: Use the errno value to determine the reason for failure.
2512-445 Syntax error: Blank required after end quote for keyword keyword .
Explanation: The keyword requires a blank after the end quote.
User Response: Correct the command file and resubmit the job.
2512-446 Syntax error: Quotes mismatched for keyword keyword .
Explanation: The quotes are mismatched for the keyword.
User Response: Correct the command file and resubmit the job.
2512-447 Syntax error: Keyword keyword is not terminated.
Explanation: The keyword is not terminated.
User Response: Correct the command file and resubmit the job.
2512-448 Syntax error: The keyword_LIMIT unit type of keyword_units is not valid.
Explanation: The type of units in the keyword value is not valid
User Response: Correct the command file and resubmit the job.
2512-449 Syntax error: The keyword_LIMIT = keyword_value integer value has too many digits. Maximum allowed is digits.
Explanation: The keyword integer value has too many digits.
User Response: Correct the command file and resubmit the job.
2512-450 Syntax error: The keyword_LIMIT = keyword_value fraction value has too many digits. Maximum allowed is digits.
Explanation: The keyword fractional value has too many digits.
User Response: Correct the command file and resubmit the job.
2512-451 Syntax error: The keyword_LIMIT = keyword_value value must be numeric.
Explanation: The keyword value must be numeric.
User Response: Correct the command file and resubmit the job.
2512-452 Syntax error: The keyword_LIMIT = keyword_value cannot contain a value of zero.
Explanation: The keyword value must be greater than zero.
User Response: Correct the command file and resubmit the job.
2512-453 Syntax error: The keyword_LIMIT value keyword_value has too many characters.
Explanation: The keyword value units has too many characters.
User Response: Correct the command file and resubmit the job.
2512-454 Syntax error: The time keyword format is invalid.
Explanation: The time format in the keyword value is not valid.
User Response: Correct the command file and resubmit the job.
2512-455 Syntax error: line.
Explanation: The line in the job control file is not valid. The syntax is unknown.
User Response: Correct the command file and resubmit the job.
2512-456 The keyword_LIMIT = keyword_value soft limit of (limit units) exceeds user hard limit (limit units).
Explanation: The soft limit in the keyword value exceeds the hard limit value.
User Response: Correct the command file and resubmit the job.
2512-457 Unable to generate a temporary file name for stdin input file.
Explanation: The command was unable to generate a temporary file name.
User Response: Determine if the user has valid file permissions. If the problem persists, report it to the system administrator.
2512-458 Unable to open command file filename for output.
Explanation: The command was unable to open the temporary command file.
User Response: Determine if the user has valid file permissions. If the problem persists, report it to the system administrator.
2512-459 Unable to unlink file filename.
Explanation: The command was unable to delete the temporary command file.
User Response: Determine if the user has valid file permissions. If the problem persists, report it to the system administrator.
2512-460 Unable to write stdin input file to temp_filename.
Explanation: The command was unable to write the stdin command file to the temporary command file.
User Response: Determine if the user has valid file permissions. If the problem persists, report it to the system administrator.
2512-461 Unexpectedly large line from stdin file.
Explanation: The stdin command file is too large.
User Response: Correct the command file and resubmit the job.
2512-462 Write error copying input command file.
Explanation: The command could not copy the stdin command file to the temporary command file.
User Response: Determine if the user has valid file permissions. If the problem persists, report it to the system administrator.
2512-465 Syntax error: The time keyword_value contains a non-numeric characters.
Explanation: The time format is not valid.
User Response: Correct the command file and resubmit the job.
2512-466 Syntax error: The start date must be 12 digits: YYMMDDhhmmss.
Explanation: The date and time format is not valid.
User Response: Correct the command file and resubmit the job.
2512-467 Syntax error: For the keyword keyword, month_value is not a valid month.
Explanation: The date format is not valid.
User Response: Correct the command file and resubmit the job.
2512-468 Syntax error: For the keyword keyword, day_value is not a valid day.
Explanation: The date format is not valid.
User Response: Correct the command file and resubmit the job.
2512-469 Syntax error: For the keyword keyword, hour_value is not a valid hour.
Explanation: The date format is not valid.
User Response: Correct the command file and resubmit the job.
2512-470 Syntax error: For the keyword keyword, minute_value is not a valid minute.
Explanation: The time format is not valid.
User Response: Correct the command file and resubmit the job.
2512-471 Syntax error: For the keyword keyword, second_value is not a valid second.
Explanation: The time format is not valid.
User Response: Correct the command file and resubmit the job.
2512-472 Syntax error: For keyword = keyword_value , the MM is not valid MM/DD/YY.
Explanation: The date format is not valid.
User Response: Correct the command file and resubmit the job.
2512-473 Syntax error: For keyword = keyword_value , the DD is not valid MM/DD/YY.
Explanation: The date format is not valid.
User Response: Correct the command file and resubmit the job.
2512-474 Syntax error: For keyword = keyword_value , the YY is not valid MM/DD/YY.
Explanation: The date format is not valid.
User Response: Correct the command file and resubmit the job.
2512-475 Syntax error: For keyword = keyword_value , the date format is not valid MM/DD/YY.
Explanation: The date format is not valid.
User Response: Correct the command file and resubmit the job.
2512-476 Unable to switch locale to locale, possibly because that locale is not installed on this system. Using locale={locale} instead.
Explanation: The command that was invoked could not switch to the locale specified in the user's environment variables. The default locale being used is specified in the message.
User Response: Ensure that the locale specified by the LC_ALL environment variable is installed on the machine where the command is being run. The command will execute but any locale information, including the message catalog, will come from the default locale.
2512-477 Unable to restore LC_COLLATE locale to original value. It will be left as: value used.
Explanation: The command could not restore the value of LC_COLLATE to its default value. The value from the user's environment will be used.
User Response: Contact the LoadLeveler administrator.
2512-478 job name could not open executable name to check for magic number.
Explanation: The job's executable could not be opened to verify it is in the correct executable file format.
User Response: Make sure the executable specified in the job is an existing file with the appropriate file access permissions.
2512-479 job name read(file descriptor, file header address,file header size) for magic number failed.
Explanation: The job's executable's XCOFF header could not be read.
User Response: Make sure the executable specified in the job is a binary executable compiled on the correct operating system platform.
2512-480 Bad magic number in xcoff header.
Explanation: The job's executable is not in XCOFF format.
User Response: Make sure the executable specified in the job is a binary executable compiled on the correct operating system platform.
2512-481 Bad a.out header size in xcoff header.
Explanation: The job's executable's a.out header could not be read.
User Response: Make sure the executable specified in the job is a binary executable compiled on the correct operating system platform.
2512-482 Read: read(executable file descriptor,a.out header address,header size) failed for job name executable.
Explanation: Read failed for job's executable.
User Response: Make sure file specified as the executable in the job command file exists and has the correct file access permissions.
2512-483 Bad magic number in a.out header.
Explanation: The job's executable has bad XCOFF format.
User Response: Make sure the executable specified in the job is a binary executable compiled on the correct operating system platform.
2512-484 job name nlist( executable name ,nl structure array address) call fails. Return code = return code, errno = error num.
Explanation: The nlist call failed for job's executable.
User Response: Executable may be stripped. Verify that the job's executable is a binary executable compiled on the correct operating system, and is not stripped.
2512-485 job name No symbol .MAIN found in executable (executable name).
Explanation: Job's executable was not linked to run with pre-LoadLeveler 2.1 checkpoint library.
User Response: Rerun the job and if the problem persists, contact IBM service.
2512-486 job name could not open executable name to check for magic number.
Explanation: The specified calling program could not open job's executable file.
User Response: Make sure executable specified in job command file exists with the correct file access permissions.
2512-487 job name could not read executable name to check for magic number, errno = error num.
Explanation: The specified calling program was unable to read the job's executable file when attempting to check its XCOFF header.
User Response: Make sure executable specified in job command file has the correct file access permissions.
2512-488 job name could not read file header of executable name to check for magic number.
Explanation: The specified calling program was unable to read job executable's file header.
User Response: Make sure executable specified in job command file has the correct file access permissions and is a binary executable compiled on the correct operating system platform.
2512-489 job name Magic number of executable executable name is not SHARE_MAGIC.
Explanation: The specified job's executable is not SHARE_MAGIC format.
User Response: Make sure executable specified in job command file is a binary executable compiled on the correct operating system platform.
2512-490 job name Executable executable name is not compiled for this architecture.
Explanation: The executable in the specified job is not compiled to run on this operating system platform.
User Response: Make sure executable specified in job command file is a binary executable compiled on the correct operating system platform.
2512-491 mbstowcs() error converting string (multibyte character input string).
Explanation: The specified command which uses the mbstowcs system call encountered an error attempting to convert the command line input from multibyte character string to wide character string.
User Response: Verify validity of multibyte character input string, and retry the command. If the problem persists, contact IBM service.
2512-492 Syntax error: error description. Discovered at line line num in file filename.
Explanation: The specified command encountered an error while parsing the command input in the specified file at the specified line.
User Response: Examine the expression in the specified file at the specified line for incorrect syntax. Correct the problem and retry the command.
2512-493 Unable to evaluate expression in function at line line num.
Explanation: The specified command encountered an internal error occurred because of a malformed expression.
User Response: Retry the command, and if the problem persists, contact IBM service.
2512-494 Expression expression name expected type string, but was expression type
Explanation: The specified command Processing a set expression expected to find a character string but found the specified type instead.
User Response: Contact the LoadLeveler administrator if the problem is not apparent from the information given.
2512-495 Input file contains string, command file line, with non-ASCII characters.
Explanation: The specified command detected non-ASCII characters in the specified file at the specified line. LoadLeveler expects all input to be ASCII characters.
User Response: Correct the command file and resubmit the job.
2512-777 XDR_Write failed, returned return_code, fd = file_descriptor, errno = error_num.
Explanation: xdr is used to transmit data among LoadLeveler commands and daemons.
User Response: Verify that the LoadLevler daemon is still running.
2512-901 Unable to set gid for user.
Explanation: The gid for the user could not be set before starting the user's job step. This message will be followed by a message giving more detail on the exact cause of the failure.
User Response: See action for following message.
2512-902 Unable to set process limits for user.
Explanation: Resource process limits could not be set before starting the user's job step. This message will be followed by a message giving more detail on the exact cause of the failure.
User Response: See action for following message.
2512-903 Unable to set resource limit limit for user.
Explanation: The specified process resource limit could not be set before starting the user's job step. This message will be followed by a message giving more detail on the exact cause of the failure.
User Response: See action for following message.
2512-904 Cannot run a job for root, uid=uid, gid=gid.
Explanation: LoadLeveler will not run any job with root privileges.
User Response: Resubmit the job as a non-root user.
2512-905 Cannot fork process for task_name. errno=error_num error_msg.
Explanation: The fork system call failed for the specified process.
User Response: Correct the problem indicated by the error number.
2512-906 Cannot set user credentials.
Explanation: Credentials for the user cannot be set for the job step. This message is usally followed by a message giving more detail on the exact cause of the failure.
User Response: See action for following message.
2512-907 Uid cannot be verified on hostname.
Explanation: The starter cannot verify that uid of the user submitting the job is valid on the machine trying to run the job step. This message will be followed by a message giving more detail on the exact cause of the failure.
User Response: The user must have the same uid on both the submitting machine and the running machine.
2512-908 Gid cannot be verified on hostname.
Explanation: The starter cannot verify that gid of the user submitting the job is valid on the machine trying to run the job step. This message will be followed by a message giving more detail on the exact cause of the failure.
User Response: The user must have the same gid on both the submitting machine and the running machine.
2512-909 Cannot get user credentials.
Explanation: Credentials for the user cannot be obtained. This message will be followed by a message giving more detail on the exact cause of the failure.
User Response: See action for following message.
2512-910 Cannot establish listen socket for Starter children. errno=error_num error_msg.
Explanation: The listen system call failed. The Starter was attempting to listen on a unix domain socket to communicate with a forked process.
User Response: Correct the problem indicated by the error number.
2512-911 Cannot receive executable from Schedd.
Explanation: A transaction from the Starter on a run machine to the Schedd on the submitmit machine to retrieve the executable file has failed.
User Response: Check SchedLog and StarterLog to determine the cause of the failure.
2512-912 Cannot open stdin, stdout, or stderr file. error_msg.
Explanation: The open system call failed for one of the stdio files for the job step.
User Response: Check that the directory and file exist and the user has permission to access the directory.
2512-913 Unable to validate privileges for stdio.
Explanation: The llcheckpriv program was unable to access a stdio file for the job step and was unable to return an error message.
User Response: Check the StarterLog for messages indicating the reason for the failure.
2512-914 Checkpointing was requested but program is not an executable.
Explanation: Only a binary program can be checkpointed. Checkpointing is not valid with a shell script.
User Response: Specified a binary program for the executable or turn off checkpointing and resubmit the job.
2512-915 Checkpointing was requested but program is not linked with LoadLeveler libs.
Explanation: Only a binary program can be checkpointed. Checkpointing is not valid with a shell script. program to be checkpointed must be linked with the LoadLeveler libraries
User Response: Link the program with the LoadLeveler libraries and resubmit the job.
2512-916 Program linked with LoadLeveler libs but checkpointing is not requested.
Explanation: The program specified as the executable is linked with the LoadLeveler executables which are used for checkpointing the program but the program will not be checkpointed because checkpointing was not requested.
User Response: Link the program without the LoadLeveler libraries or turn on checkkpointing and resubmit the job.
2512-917 Cannot exec process for task_name. errno=error_num error_msg.
Explanation: The exec system call failed for the specified process.
User Response: Correct the problem indicated by the error number.
2512-918 Unable to set uid for user.
Explanation: The uid for the user could not be set before starting the user's job step. This message will be followed by a message giving more detail on the exact cause of the failure.
User Response: See action for following message.
2512-919 Cannot receive job data from schedd on hostname.
Explanation: An error occured as the starter was request the job information from the schedd on the specified host.
User Response: Check the schedd log and the starter log on the appropriate machine for the exact cause of the failure.
2512-920 Cannot send READY status to the startd, the job step will be rejected.
Explanation: An error occured as the starter was attempting to send the READY status to the startd. Since the a parallel job step will not continue until all nodes are READY the job step will be rejected.
User Response: Check the starter log and the starter log for the exact cause of the failure.
2512-921 Job was not accepted by NQS.
Explanation: An error occured when a job was submitted to NQS.
User Response: Check the output from the qsub command for the exact cause of the failure.
2512-922 The LoadL_starter process terminated before the job step completed. The job step is vacated.
Explanation: The LoadL_starter process which started a job step has abnormally terminated while waiting for the job step to complete. Since the true status of the job step cannot be determined the job step is vacated. The vacated job step will be rescheduled to run if it is marked restartable.
User Response: Examine the LoadLeveler logs for the appropriate machine to determine the cause to the LoadL_starter failure.
2512-923 Cannot create PVM control file filename, errno = error num error message.
Explanation: The file necessary to start the PVM daemon (pvmd) could not be created.
User Response: Correct the problem indicated by the error number.
2512-924 Cannot get PVM task id on host name, PVM error = PVM error num, errno=error num error message.
Explanation: The PVM function, pvm_mytid, failed to return the PVM task id for the specified host.
User Response: Correct the problem indicated by the PVM or system error number.
2512-925 Cannot get PVM socket, PVM error = PVM error num, errno=error num [error message.
Explanation: The PVM function, pvm_getfds, failed to return the file desciptor for the socket to the PVM daemon (pvmd) on the master node.
User Response: Correct the problem indicated by the PVM or system error number.
2512-926 Cannot register as PVM hoster, PVM error = PVM error num, errno=error num [error message.
Explanation: The PVM function, pvm_reg_hoster, failed. This function is used to inform PVM that LoadLeveler will select all the hosts and start the PVM daemon (pvmd) on all hosts.
User Response: Correct the problem indicated by the PVM or system error number.
2512-927 Cannot return PVM response to master starter, errno=error num [error msg.
Explanation: A remote Starter could not send a PVM message to the master Starter.
User Response: Correct the problem indicated by system error number.
2512-928 PVM daemon is already running on hostname, task id = PVM task ID
Explanation: A PVM daemon (pvmd) is already running on the specified host. When running PVM under LoadLeveler only one PVM job can be run on a host at a time.
User Response: Stop PVM on the specified host and resubmit the job.
2512-929 Cannot remove old PVM socket file, filename, on hostname, errno = error num error msg.
Explanation: The socket file left from a previous PVM session cannot be removed so PVM cannot be started on the host.
User Response: Correct the problem indicated by system error number.
2512-930 Cannot read start host message from PVM. Cannot start PVM on remote host.
Explanation: LoadLeveler received a start host message (SM_STHOST) from PVM but the message was not in a valid format.
User Response: Check the correct version of PVM is installed properly and resubmit the job.
2512-931 Request to start PVM on host hostname failed. The host was not found in LoadLeveler's host list.
Explanation: LoadLeveler received a start host message (SM_STHOST) from PVM but the host name was not valid.
User Response: Check the correct version of PVM is installed properly and resubmit the job.
2512-932 Cannot send start PVM request to Startd on hostname,errno = error num error msg.
Explanation: The master Starter cannot send a request to the Startd on the specified node to start the PVM daemon (pvmd).
User Response: Correct the problem indicated by the error number.
2512-933 PVM could not be started on remote host hostname,errno = error num error msg.
Explanation: The master Starter either could not receive the start up message from the remote Starter or the PVM daemon (pvmd) could not be started on the remote host.
User Response: If the error number indicates a network problem resubmit the job after the problem has been corrected. Otherwise check the Starter log on the remote node for the cause of the failure.
2512-934 Unable to set uid for user on hostname.
Explanation: The uid for the user could not be set before starting the user's job step. This message will be followed by a message giving more detail on the exact cause of the failure.
User Response: See action for following message.
2539-001 Could not open input file (/dev/null) for pipe input.
Explanation: The command open(("/dev/null", O_RDONLY)) failed.
User Response: Contact the LoadLeveler administrator.
2539-002 command was not executed.
Explanation: xloadl attempted unsuccessfully to execute a system command.
User Response: Reason for this error should be displayed immediately preceding this message.
2539-003 Could not create stdout pipe from command, errno = error_num.
Explanation: Executing a pipe command failed.
User Response: Check the errno to determine why the command failed.
2539-004 Could not create stderr pipe from command, errno = error_num.
Explanation: Executing a pipe command failed.
User Response: Check the errno to determine why the command failed.
2539-005 Could not fork process for command, errno = error_num.
Explanation: An error occurred while attempting to fork the command.
User Response: Check the errno to determine why the fork failed.
2539-006 Could not execute command command. errno=error_num.
Explanation: An error occurred while attempting to execute the command.
User Response: Check the errno to determine why the command failed.
2539-007 Not a valid selection. Field is not set.
Explanation: The field was not updated because the value entered was not one of the valid values for this field.
User Response: Re-enter a value for the selection by selecting a value from the selection box. If you typed a value, check the spelling to ensure it matches a valid value.
2539-008 Logging has already been started to file filename.
Explanation: Logging cannot be started because commands are being logged to the specified file at this time.
User Response: No action is needed if you want logging to take place to the specified file. If you want to begin logging to another file, select Stop Logging and then Start Logging with your new file specified.
2539-009 No jobs are selected.
Explanation: The tasks you want to perform require that at least one job step be selected.
User Response: Select a job step and invoke the command again.
2539-010 Could not get details for selected jobs.
Explanation: The information for the selected jobs was not returned.
User Response: Consult preceding error messages for possible causes. If there are none, check to see if the job step has completed.
2539-011 Could not get Status for selected jobs.
Explanation: The information for the selected jobs was not returned.
User Response: Consult preceding error messages for possible causes. If there are none, check to see if the job step has completed.
2539-012 Could not get Report for selected jobs.
Explanation: The information for the selected jobs was not returned.
User Response: Consult preceding error messages for possible causes. If there are none, check to see if the job step has completed.
2539-013 No host specified. No selection performed.
Explanation: Although one of the by_host job_filters has been indicated, no indication of which machines have been provided.
User Response: The previous setting for filtering jobs will be used. Respecify the new filter using Selecton the menu bar.
2539-014 The selection parameter was not changed.
Explanation: No matches were found, so the jobs were not filtered. There may be a problem with the regular expression or there may be no machines which match the regular expression.
User Response: If there is a problem with the regular expression, a message explaining that will precede this one. You may need to adjust the regular expression.
2539-015 No user specified. No selection performed.
Explanation: Although one of the by_user job_filters has been indicated, no indication of which users have been provided.
User Response: The previous setting for filtering jobs will be used. Respecify a new filter using Selecton the menu bar.
2539-016 No group specified. No selection performed.
Explanation: Although one of the by_group job_filters has been indicated, no indication of which groups have been provided.
User Response: The previous setting for filtering jobs will be used. Respecify a new filter using Select on the menu bar.
2539-017 No job specified. No selection performed.
Explanation: Although one of the by_... job_filters has been indicated, no indication of which job step ids have been provided.
User Response: The previous setting for filtering jobs will be used. Respecify a new filter using Select on the menu bar.
2539-018 Internal error: filter_type is not a valid filter.
Explanation: A value that is not valid is being used as the filter type.
User Response: Exit and restart xloadl.
2539-019 No user specified. Order user not performed.
Explanation: A favor user command cannot be issued with a blank user name.
User Response: Type a user name in the text field of the prompt dialog.
2539-020 Only the LoadLeveler administrator may order users.
Explanation: You must be a LoadLeveler administrator to order users.
User Response: Have a LoadLeveler adminstrator issue this command.
2539-021 Unknown pulldown number: pulldown_num.
Explanation: The item selected on the pulldown has translated into an unrecognized number.
User Response: Exit and restart xloadl.
2539-022 Could not get tasks for selected jobs.
Explanation: The information for the selected jobs was not returned.
User Response: Consult preceding error messages for possible causes. If there are none, check to see if the job step has completed.
2539-025 No machine is selected.
Explanation: The task you want to perform require that at least one machine be selected.
User Response: Select a machine from the Machines window and invoke the command again.
2539-026 No schedd machine specified. No purge performed.
Explanation: A schedd machine needs to be specified for the purge command.
User Response: Enter a machine name into the Purge Machine dialog.
2539-027 No machines selected. No machines will be purged.
Explanation: At lease one machine needs to be specified for the purge command.
User Response: Select a machine from the Machines window and invoke the purge command again.
2539-028 No host is selected for details.
Explanation: At lease one machine needs to be specified for the details command.
User Response: Select a machine from the Machines window and invoke the command again.
2539-029 Could not get details for selected machines.
Explanation: No details were returned for the selected machines.
User Response: Consult preceding messages for reason details were not returned.
2539-031 No host selected for Version.
Explanation: At least one machine needs to be specified for the Version command.
User Response: Select a machine from the Machines window and invoke the command again.
2539-032 Could not get Version for selected machines.
Explanation: No version information was returned for the selected machines.
User Response: Consult preceding messages for reason Version information was not returned.
2539-033 No host selected for Collecting data.
Explanation: At lease one machine needs to be specified for the Capture Data command.
User Response: Select a machine from the Machines window and invoke the command again.
2539-034 No Operating System specified. No selection performed.
Explanation: To change the Selection filter to by Operating System you must specify an Operating System. The value returned was NULL, so the filter was not changed.
User Response: Use the Select pulldown in the Machines Window to reset the Selection filter.
2539-035 No Architecture specified. No selection performed.
Explanation: To change the Selection filter to by Architecture, you must specify an Operating System. The value returned was NULL, so the filter was not changed.
User Response: Use the Select pulldown in the Machines Window to reset the Selection filter.
2539-036 No host selected for Capture.
Explanation: At lease one machine needs to be specified for the Capture Data command.
User Response: Select a machine from the Machines window and invoke the command again.
2539-038 Value of resource_name is not valid, resetting from resource_value to default_value.
Explanation: Because the value of the Resource is not valid, a default value is used.
User Response: If the default value is not acceptable to you, exit xloadl, change the value of the Resource in your Xloadl or .Xdefaults file, and re-invoke xloadl.
2539-039 No ADMIN_FILE specified in LoadL_config. Cannot start LoadLeveler.
Explanation: LoadLeveler cannot start without an admin file.
User Response: Add an ADMIN_FILE keyword and value to your configuration file. For example, "ADMIN_FILE = /u/loadl/LoadL_admin".
2539-040 Could not read machine list from admin file.
Explanation: There is a problem reading machine information from the admin file.
User Response: Check the machine stanzas in the admin file.
2539-041 Can not get configuration information. xloadl cannot continue.
Explanation: Because it could not get configuration information, xloadl cannot start.
User Response: Ensure the LoadL_admin and LoadL_config files are available and accessible.
2539-042 LOADL_ADMIN not specified in config file. No administrator commands will be permitted.
Explanation: Since there are no LoadLeveler administrators identified in the config file, no adminstrator commands are allowed.
User Response: Exit xloadl and re-invoke it after administrators have been specified in the config file. For instance, LOADL_ADMIN = loadl.
2539-043 Unable to malloc() num bytes of memory.
Explanation: Not enough storage space was available to perform the allocation.
User Response: Make more storage available.
2539-044 Error returned on regular expression match.
Explanation: An error was returned while trying to match a regular expression used as a job selection filter.
User Response: Modify the regular expression.
2539-045 Could not contact daemon_name on hostname.
Explanation: Could not contact the daemon specified to get job information.
User Response: Check to see if the daemon is running.
2539-046 Error receiving job data.
Explanation: A request for job information has been unsuccessful. If data was returned, it may be incomplete.
User Response: Re-issuing the command or refreshing the Jobs window may resolve the problem. If it persists, try exiting and re-invoking xloadl.
2539-047 Cannot read machine information from central manager.
Explanation: An error occurred while machine information was being sent to xloadl from the central manager.
User Response: Re-do the action.
2539-048 Could not send command to cm host.
Explanation: xloadl was able to connect to the central manager, but was not able to successfully send a command to it.
User Response: Consult preceding messages for the reason for the failure.
2539-049 Could not connect to daemon_name on hostname. Will reconfig xloadl and retry.
Explanation: On the first failure to contact a daemon, xloadl will reconfig itself and try to contact the daemon again. The cluster may have been reconfigured since xloadl was invoked.
User Response: No action needed.
2539-050 Could not connect to daemon_name on hostname. Will retry later.
Explanation: No update to the Machines window was made because the daemon was not successfully contacted. Another attempt will be made after the automatic refresh interval.
User Response: No action needed.
2539-051 Access to this job is denied.
Explanation: You cannot issue commands for this job.
User Response: None.
2539-052 You do not own Job job_id step_id. Access to this job denied.
Explanation: You cannot issue commands for this job step, because you do not own it.
User Response: Contact the job owner or an administrator.
2539-053 Job job_id step_id in System Hold. Access to this job denied.
Explanation: You cannot access this job because a System Hold has been put on it.
User Response: Contact the LoadLeveler adminstrator.
2539-054 Only the LoadLeveler administrator may order jobs.
Explanation: Only LoadLeveler administrators have the authority to order jobs using the favor job command.
User Response: Contact the LoadLeveler adminstrator.
2539-055 Unrecognized ORDER type order_type. No action taken.
Explanation: The order type is not valid for favor jobs or users.
User Response: Re-issue the command. If the same message occurs, exit from xloadl and re-start it.
2539-056 Could not send command to daemon_name on machine_name.
Explanation: An unsuccessful attempt was made to send a command to the daemon.
User Response: Check to see if the daemon is active. Re-issue the command. If the same message occurs, exit from xloadl and re-start it.
2539-057 Only the LoadLeveler administrator may order users.
Explanation: You do not have authority to issue this command.
User Response: A LoadLeveler administrator can issue this command.
2539-058 Error receiving machine data.
Explanation: A request for machine information has been unsuccessful. If data was returned, it may be incomplete.
User Response: Re-issuing the command or refreshing the Machines window may resolve the problem. If it persists, try exiting and re-invoking xloadl.
2539-059 Only the LoadLeveler administrator may issue LoadLeveler control commands.
Explanation: You do not have authority to do this action.
User Response: A LoadLeveler administrator has the authority to do this.
2539-060 Can not find name of executable for LoadL_master in config file.
Explanation: Did not find name of executable for LoadL_master in configuration file.
User Response: Update the keyword MASTER in the configuration file. For example, MASTER = $(BIN)/LoadL_master. Then reconfigure or restart LoadLeveler.
2539-061 Could not send command.
Explanation: The command to restart LoadLeveler could not be sent to the Master daemon on the selected machine.
User Response: Resolve why the command cannot be sent or login to the selected machine and start LoadLeveler there.
2539-062 No machines selected. No machines purged.
Explanation: If no machines are selected, a purge cannot occur.
User Response: Select at least one machine and rerun the command.
2539-063 Could not get class information for machine name.
Explanation: No classes were returned for the selected machine due to internal errors.
User Response: Re-issuing the command or refreshing the Machines window may resolve the problem. If it persists, try exiting and re-invoking xloadl.
2539-064 Cannot obtain this host name. Job not submitted.
Explanation: The official hostname for this machine is not set.
User Response:
2539-065 Cannot find password entry for your userid. Job not submitted.
Explanation: The get_userid() call returned a value of NULL.
User Response:
2539-066 Cannot find your userid in /etc/passwd. Job not submitted.
Explanation: The getpwuid() or getuid() call returned a value of NULL.
User Response:
2539-067 Not valid user priority, input, is ignored.
Explanation: The value you typed into the text field for user priority is not a valid value for user priority.
User Response: Type a value between 0 and 100 into the field for user priority.
2539-068 Previously set user priority value, user_priority, is used.
Explanation: The value you wanted to replace the user priority is not valid, so the previously set value is used.
User Response: If you want to change the value, type a value between 0 and 100 into the field for user priority.
2539-069 The maximum value for user priority, 100, is used instead of input_value.
Explanation: The value you typed is greater than 100, the maximum value for user priority. It has been replaced by the maximun value.
User Response: If you want the user priority to be a value other than 100, type a value between 0 and 100 into the field for user priority.
2539-070 min_processors value of num is not valid. It is ignored.
Explanation: The value for min_processors is not valid. The default, 1, is used.
User Response: Enter a non-negative number in the min_processors field.
2539-071 max_processors value of num is not valid. It is ignored.
Explanation: The value for max_processors is not valid. The default, 1, is used.
User Response: Enter a non-negative number in the max_processors field.
2539-072 Unrecognized job primary sort request: sort_type.
Explanation: The value in the message is not recognized as a sort type.
User Response: Stop and restart xloadl...
2539-073 Unrecognized job secondary sort request: sort_type.
Explanation: The value in the message is not recognized as a sort type.
User Response: Stop and restart xloadl...
2539-074 Unrecognized machine primary sort request: sort_type.
Explanation: The value in the message is not recognized as a sort type.
User Response: Stop and restart xloadl...
2539-075 Unrecognized machine secondary sort request: sort_type.
Explanation: The value in the message is not recognized as a sort type.
User Response: Stop and restart xloadl...
2539-076 Central manager is defined on machine_name. Cannot connect to LoadLeveler Central Manager.
Explanation: The central manager is defined on the specified machine; however xloadl cannot connect to it.
User Response: Check to see if the Central Manager is active.
2539-077 Cannot find a central manager.
Explanation: xloadl did not locate any central manager.
User Response: Exit xloadl, re-start it, and rerun the command. If no central manager is still found, contact your LoadLeveler admin.
2539-078 Entire Script may not have been saved.
Explanation: The number of bytes saved less than the number in the file.
User Response: Try to save the script again. Ensure there is enough space.
2539-079 Unable to save Script. Error in creating tempfile.
Explanation: The script could not be saved to a temporary file.
User Response: Check /tmp to ensure that there is enough space and permissions allow saving a file here.
2539-080 You are not a LoadLeveler Administrator. You cannot access Job machine_name job_id step_id.
Explanation: You need to be a LoadLeveler Administrator to perform this task.
User Response: You cannot perform this task.
2539-081 You do not have the needed admin privileges and you do not own this job. You cannot access Job machine_name job_id step_id.
Explanation: To perform this task you need to own the job or have sufficient priviledges.
User Response: You cannot perform this task.
2539-082 You do not have the needed admin privileges.
Explanation: To perform this task you need to have sufficient LoadLeveler, group or class administrative privileges.
User Response: You cannot perform this task.
2539-083 No valid jobs selected. Command not sent.
Explanation: The command was not executed because there were no valid jobs selected for it.
User Response: Select at least one job and reissue the command. You may want to refresh the Jobs window before doing so to ensure the status presented there is more up to date.
2539-084 The length of the regular expression must be less than 1024 bytes.
Explanation: The length of regular expressions entered in xloadl must be less than 1024 bytes.
User Response: Enter a shorter regular expression.
2539-085 Problem with regular expression, regular_expression : error_msg.
Explanation: String2 describes a problem with the regular expression in string1.
User Response: Use the message in string2 to determine the cause of the error and correct it.
2539-086 Problem with regular expression, regex.h error no. = error_code.
Explanation: There is a problem with your regular expression which is described by the error code.
Explanation: Consult /usr/include/regex.h for the error codes and their meanings.
2539-087 Problem with regular expression:
Explanation: There is a problem with your regular expression which is described by the error message.
User Response: Use the message in string2 to determine the cause of the error and correct it.
2539-088 Could not get classes for task_name.
Explanation: The classes that apply to the task you are trying to perform were not returned due to internal errors. Consult the preceding messages for the reason. described by the error message.
User Response: Address the cause of the preceding messages.
2539-089 Min # of Nodes must be less than Max # of Nodes.
Explanation: The value you have in the Nodes window for maximum number of
User Response: Modify one of the values.
2539-090 A range of nodes is not valid when Total Tasks is specified.
Explanation: You have entered values for the minimum and maximum number of nodes as well as total task in the Nodes Window. A range of nodes is not valid when Total Tasks are specified.
User Response: Modify the values so that the maximum and minimum are the same or unset values so the conflict no longer exists.
2539-091 Minimum number of nodes, field value, is not valid. It is ignored.
Explanation: The value for the text field for minimum number of nodes is not a valid value for this field.
User Response: Modify the value to an integer that is greater than zero.
2539-092 Maximum number of nodes, field value, is not valid. It is ignored.
Explanation: The value for the text field for maximum number of nodes is not a valid value for this field.
User Response: Modify the value to an integer that is greater than minimum number of nodes.
2539-093 Tasks Per Node, field value, is not valid. It is ignored.
Explanation: The value for the text field for Tasks Per Node is not a valid value for this field.
User Response: Modify the value to an integer that is greater than zero.
2539-094 Total Tasks, field value, is not valid. It is ignored.
Explanation: The value for the text field for Total Tasks is not a valid value for this field.
User Response: Modify the value to an integer that is greater than zero.
2539-095 Minimum number of processors, field value, is not valid. It is ignored.
Explanation: The value for the text field for minimum number of processors is not a valid value for this field.
User Response: Modify the value to an integer that is greater than zero.
2539-096 Maximum number of processors, field value, is not valid. It is ignored.
Explanation: The value for the text field for maximum number of processors is not a valid value for this field.
User Response: Modify the value to an integer that is greater than minimum number of processors.
2539-097 Node Usage, field value, is not valid. It is ignored.
Explanation: The value for the text field for Node Usage is not a valid value for this field.
User Response: Modify the value. Support values are "shared" and "not_shared."
2539-120 Could not get classes for task name.
Explanation: The classes that apply to the task you are trying to perform were not returned due to internal errors. Consult the preceding messages for the reason.
User Response: Address the cause of the preceding messages.
2539-130 Adapter preference is not supported. It is ignored.
Explanation: Your input contains a Preferences line which has an Adapter keyword in it. The Preferences line is ignored due to the unsupported keyword.
User Response: Remove the Adapter Preference from the input.
2539-131 Cannot open file filename errno=error num. Using built-in defaults.
Explanation: The open system call failed for the specified file. Defaults will be used in the Job Builder instead of information from your file.
User Response: Check that the directory and file exist and the user has permission to access the directory.
2539-132 notification option is not a valid notification option. It is ignored.
Explanation: Your file specifies an option for the notification keyword that is not recognized.
User Response: Check to ensure a valid option is specified. The values are user_initiated, system_intiated, no.
2539-133 checkpoint option is not a valid checkpoint option. It is ignored.
Explanation: Your file specifies an option for the checkpoint keyword that is not recognized.
User Response: Check to ensure a valid option is specified. The values are user_initiated, system_intiated, no.
2539-134 restart option is not a valid Restart option. It is ignored.
Explanation: Your file specifies an option for the Restart keyword that is not recognized.
User Response: Check to ensure a valid option is specified. The values are yes, no.
2539-135 Requirements line in input file is not valid. It is ignored.
Explanation: The Requirements line specified in your file is not valid, so that line is ignored and the information is not displayed in the Job Builder.
User Response: Check that the line includes only the following keywords: Memory, Feature, Machine, Disk, Arch, OpSys, Adapter, Pool. The line must be in the form of a Boolean expression.
2539-136 Adapter can only occur once in a valid Requirements line. The Requirements line is ignored.
Explanation: A Requirements line is not valid is if there is more than one Adapter specified in the line.
User Response: Rewrite the line so that only one Adapter is specified or remove the Adapter specifications from the Requirements line and use the network specification instead.
2539-137 The "Preferences" line in input file is ignored because Adapter Preferences are not valid.
Explanation: The Preferences line specified in your file is not valid, so that line is ignored and the information is not displayed in the Job Builder.
User Response: Remove Adapter from the Preferences line.
2539-138 Preference line in input file is not valid. It is ignored.
Explanation: The Preferences line specified in your file is not valid, so that line is ignored and the information is not displayed in the Job Builder.
User Response: Check that the line includes only the following keywords: Memory, Feature, Machine, Disk, Arch, OpSys, Pool. The line must be in the form of a Boolean expression.
2539-139 option is not a valid job type option. It is ignored.
Explanation: Your file specifies an option for the job_type keyword that is not recognized.
User Response: Check to ensure a valid option is specified. The values are pvm3, parallel, serial.
2539-140 Problem setting network network protocol from input file name. It is ignored.
Explanation: There was a problem transforming the network information in your file into a Job Builder window.
User Response: Set the information in the Network window (for mpi, lapi) or the PVM window (for pvm).
2539-141 network type is not a valid network type. The network keyword is ignored.
Explanation: Your file specifies an adapter name or network type which is not valid.
User Response: Check to ensure a valid name or type is specified. The values are specified as adapter names or network types on the Adapter stanzas in the LoadL admin file.
2539-142 adapter usage or node is not a valid adapter usage or mode. It is ignored.
Explanation: Your file specifies an adapter usage or mode which is not valid.
User Response: Check to ensure a valid value is specified. The values for usage are shared and not_shared. The values for mode are IP and US.
2539-143 The adapter usage or node keyword in filename is not supported by the job builder.
Explanation: Your file specifies a keyword that is not recognized. It is ignored by the Job Builder.
User Response: Check to ensure a valid value is specified.
2539-144 Cannot read the default file, xloadl default file.
Explanation: Unable to open file.
User Response: Check for various conditions.... File might not exist, permissions might prohibit opening, no file descriptors may be available, etc. To change the defaults file, modify the Xloadl resource "skelfile".
2539-145 Could not get details for selected class.
Explanation: The information for the selected jobs was not returned.
User Response: Consult preceding error messages for possible causes. If there are none, attempt to run the command again or run llclass -l classname from the command line.
2539-146 No Class Choices are available.
Explanation: No classes were returned for display in Class Choices Selection Box.
User Response: This message appears if no Classes are configured in the LoadL admin file. Preceding error messages may indicate if a problem has occurred obtaining the data.
2539-150 The Adapter adapter name or network type in the Requirements line is ignored because there is already a network keyword in the job cmd file.
Explanation: A network statement has already been restored into the Job Builder. Since only one is supported in a job cmd file, the Adapter statement cannot be converted into a network statement.
User Response: Update your input file so it contains only one network or Adapter keyword or check in the Network or PVM window in the Job Builder to ensure Adapter/Network reflects the adapter you wish to use.
2539-151 The Adapter adapter name or network type in the Requirements line is ignored because it is not recognized.
Explanation: The Adapter type referred to in the Requirements line is not recognized. It must be an Adapter name or network type from an Adapter stanza in the administration file.
User Response: Update the Adapter with a configured adapter name or replace it with a network specification for a valid adapter type in your input file or set the Adapter using the Network or PVM window in the Job Builder.
2539-152 The Adapter adapter name or network type in the Requirements line is ignored because it is not configured.
Explanation: The Adapter type referred to in the Requirements line is not valid. It must be an Adapter name or network type from an Adapter stanza in the administration file.
User Response: Update the Adapter with a configured adapter name or replace it with a network specification for a valid adapter type in your input file or set Adapter/Network in the Network or PVM window in the Job Builder.
2539-153 The Requirements line is ignored because there is already a network keyword in the input file.
Explanation: A network statement has already been restored into the Job Builder. Since only one is supported in a job cmd file, the Adapter statement cannot be converted into a network statement.
User Response: Update your input file so it contains only one network or Adapter keyword or check the Network or PVM window in the Job Builder to ensure it reflects the adapter you wish to use and update the Requirements window for other requirements.
2539-154 Cannot set both Adapter Requirement and Network.
Explanation: There is already an Adapter keyword on the Requirements line. Since only one of Adapter Requirement and Network is supported in any job cmd file, entering adapter information into the Network or PVM window is prevented. This message will only appear once.
User Response: Remove the Adapter keyword from the Requirements input field in the Requirements window, if you wish to enter adapter information in the Network or PVM window.
2539-155 The keyword keyword from your input file is not supported by the scheduler type scheduler. It is ignored.
Explanation: This keyword from your input file is not supported by the scheduler currently running. The keyword is ignored and will not appear in the Job Builder.
User Response: None.
2539-156 The Adapter adapter type in the Requirements line is ignored. It cannot be converted to a network.PVM statement.
Explanation: The Adapter type referred to in the Requirements line cannot be converted to a network.PVM statement. It is ignored and will not appear in the Job Builder.
User Response: Update the network information in the PVM window of the Job Builder as needed.
2539-157 Cannot set US Mode in a network.PVM statement. Mode is ignored.
Explanation: The Adapter type referred to in the Requirements line cannot be converted to a network.PVM statement. It is ignored and will not appear in the Job Builder.
User Response: Update the network information in the PVM window of the Job Builder as needed.
2539-158 The network statement in your input file is ignored because an Adapter Requirement was converted to a network statement.
Explanation: While filling Job Builder fields from your input file, an Adapter keyword on the Requirements line has been converted to a network keyword. Since only one of Adapter Requirement and Network is supported in any job cmd file, the network statement is ignored.
User Response: Go to the Network window and adjust the settings as needed.
2539-201 The file AFS_loadable_object_path was not found. If this is a submit only machine using AFS then the file must exist.
Explanation: LoadLeveler uses an loadable object to contain code for fetching and setting afs tokens. The loadable object was not found when LoadLeveler attempted to load it.
User Response: Ensure the LoadLeveler afs loadable object is installed and repeat command.
2539-231 Job Switch Resource Table could not be loaded on node node_name for the following reason:
Explanation: The Job Switch Resource Table for a job could not be loaded on the specified machine.
User Response: Correct the problem indicated by the error message.
2539-232 Job Switch Resource Table could not be loaded on nodenode_name because the switch is in use and can not be freed.
Explanation: The Job Switch Resource Table for a job could not be loaded on the specified machine because the switch is already in use and attempts to free the switch have failed.
User Response: Check the switch table log in /var/adm/SP/logs/st/st_log for the cause of the failure.
2539-233 Job Switch Resource Table could not be loaded on node node_name due to a system error, st_load_table returned error return_code.
Explanation: The Job Switch Resource Table for a job could not be loaded on the specified machine because of a system error.
User Response: Check the switch table log in /var/adm/SP/logs/st/st_log for the cause of the failure.
2539-234 Job Switch Resource Table could not be loaded on node node_name due to an internal error, st_load_table returned error return_code.
Explanation: The Job Switch Resource Table for a job could not be loaded on the specified machine because of an internal error.
User Response: Report the failure to IBM service.
2539-235 Job Switch Resource Table could not be unloaded on node node_name due to a system error, st_unload_table returned error return_code.
Explanation: The Job Switch Resource Table for a job could not be unloaded on the specified machine because of a system error.
User Response: Check the switch table log in /var/adm/SP/logs/st/st_log for the cause of the failure.
2539-236 Job Switch Resource Table could not be unloaded on node node_name due to an internal error, st_unload_table returned error return_code.
Explanation: The Job Switch Resource Table for a job could not be unloaded on the specified machine because of an internal error.
User Response: Report the failure to IBM service.
2539-237 Job Switch Resource Table could not be unloaded on node node_name for the following reason:
Explanation: The Job Switch Resource Table for a job could not be unloaded on the specified machine.
User Response: Correct the problem indicated by the error message.
2539-238 Job Switch Resource Table could not be removed on node node_name due to a system error, st_clean_table returned error return_code.
Explanation: The Job Switch Resource Table for a job could not be removed on the specified machine because of a system error.
User Response: Check the switch table log in /var/adm/SP/logs/st/st_log for the cause of the failure.
2539-239 Job Switch Resource Table could not be removed on node node_name due to an internal error, st_clean_table returned error return_code.
Explanation: The Job Switch Resource Table for a job could not be removed on the specified machine because of an internal error.
User Response: Report the failure to IBM service.
2539-240 Job Switch Resource Table could not be removed on node node_name for the following reason:
Explanation: The Job Switch Resource Table for a job could not be removed on the specified machine.
User Response: Correct the problem indicated by the error message.
2539-241 Could not determine status for switch adapter adapter_name . st_query_adapter failed with rc return_code.
Explanation: The switch table service (st_query_adapter) failed to obtain and return the status of the switch. The switch will be treated as NOT_READY.
User Response: Correct the problem indicated by the error message.
2539-242 Could not determine status for switch adapter adapter_name for the following reason:
Explanation: The status of the switch could not be determined due to the indicated error. The switch will be treated as NOT_READY.
User Response: Correct the problem indicated by the error message.
2539-243 Failed to route specification specification name (specification number).
Explanation: LoadLeveler internal routing error.
User Response: If problem persists, call IBM Service.
2539-244 Failed to route expression for specification name (specification number).
Explanation: LoadLeveler internal routing error.
User Response: If problem persists, call IBM Service.
2539-245 Internal error, cannot find tree for configuration type configuration type.
Explanation: Internal LoadLeveler error.
User Response: If problem persists, call IBM Service.
2539-246 Unknown stanza type configuration type.
Explanation: Invalid value defined for stanza type.
User Response: Validate correctness of stanzas in LoadL_admin file.
2539-247 Cannot make a new stanza of type stanza type.
Explanation: Internal LoadLeveler error.
User Response: If problem persists, call IBM Service.
2539-248 Error refreshing stanza name stanza with defaults.
Explanation: Internal LoadLeveler error.
User Response: If problem persists, call IBM Service.
2539-249 Error merging first stanza name stanza with second stanza name stanza.
Explanation: Internal LoadLeveler error.
User Response: If problem persists, call IBM Service.
2539-250 Error inserting intlist. Element is not an array.
Explanation: Internal LoadLeveler error.
User Response: If problem persists, call IBM Service.
2539-251 Error inserting stringlist. Element is not an array.
Explanation: Internal LoadLeveler error.
User Response: If problem persists, call IBM Service.
2539-252 Error writing stanza stanza name.
Explanation: Internal LoadLeveler error.
User Response: If problem persists, call IBM Service.
2539-253 Cannot write config file config file name.
Explanation: Error writing to configuration file.
User Response: Check for existence of file and access permissions.
2539-254 Cannot write final record for file file name.
Explanation: Error writing to named file.
User Response: Check for existence of file and access permissions.
2539-255 Verify is not implemented for the stanza name stanza.
Explanation: Internal LoadLeveler error.
User Response: If problem persists, call IBM Service.
2539-256 Error writing stanza type stanza type .
Explanation: Internal LoadLeveler error.
User Response: If problem persists, call IBM Service.
2539-257 Error reading file file name.
Explanation: Failed to read user's preferred configuration file.
User Response: Check file permissions and existence.
2539-258 Username user name not in passwd file.
Explanation: Default LoadLeveler user name cannot be found in /etc/passwd.
User Response: Make sure default LoadLeveler user name exists in system.
2539-259 Groupid group id not in group file.
Explanation: Default LoadLeveler group id cannot be found in /etc/group.
User Response: Make sure default LoadLeveler group name exists in system.
2539-260 Group group name not in group file.
Explanation: Default LoadLeveler group name cannot be found in /etc/group.
User Response: Ensure default LoadLeveler group name exists on system.
2539-261 Unable to obtain name of operating system from configuration file.
Explanation: Unable find value for OpSys in configuration file.
User Response: Define a value for OpSys.
2539-262 Error processing config file configuration file name at line line number.
Explanation: Error parsing configuration file.
User Response: Check configuration file syntax at line number where error occurred.
2539-263 Local configuration file not specified in LoadL_config. Proceeding...
Explanation: No LoadL_config.local file was defined in the global LoadL_config file.
User Response: Define LoadL_config.local files on machines which are to override defaults in global LoadL_config file.
2539-264 Error processing local configuration file file name! Proceeding ...
Explanation: Error processing LoadL_config.local. Values will be used from global LoadL_config instead.
User Response: Check LoadL_config.local syntax.
2539-265 The above line in config file is too long. It must be less than 2048 bytes.
Explanation: The identified line is too long.
User Response: Keep individual lines under 2K bytes in length.
2539-266 Exiting ...
Explanation: Program is exiting.
User Response: Refer to previous error message for cause.
2539-267 Error in configuration file file name, line line number: Illegal identifier: illegal string.
Explanation: Syntax error in configuration file.
User Response: Check identified line number for error.
2539-268 Attention: keyword keyword from local configuration file, filename, will be ignored.
Explanation: Invalid keyword encountered.
User Response: Check configuration file for invalid keywords.
2539-269 Out of memory.
Explanation: Severe error - out of memory.
User Response: Make memory available.
2539-270 Expression syntax error in config file file name, line line number.
Explanation: Bad expression syntax.
User Response: Correct the expression at the indicated line number.
2539-271 Configuration file line too long.
Explanation: Line longer than 2048 bytes.
User Response: Check configuration file for lines that exceed 2048 bytes in length
2539-272 Attention: Line length is greater than 8191 bytes. Input data may be truncated.
Explanation: Line longer than 8K bytes.
User Response: Check configuration file for lines that exceed 8191 bytes in length
2539-273 Error in configuration file file name, line line number: Syntax error.
Explanation: Syntax error in configuration file.
User Response: Check identified line number for error.
2539-274 gethostname routine failed, errno = errno.
Explanation: LoadLeveler gethostname routine failed.
User Response: Internal LoadLeveler error. If problem persists, call IBM Service
2539-275 host.domain string length exceeds length.
Explanation: Invalid domain length in LoadL_admin.
User Response: Check machine domain names in LoadL_admin file for correctness.
2539-276 Unable to calloc number of bytes bytes for new hostent h_aliases array.
Explanation: Out of memory.
User Response: Make adequate memory available.
2539-277 Unable to re-allocate number of bytes bytes for new hostent h_aliases array.
Explanation: Out of memory.
User Response: Make adequate memory available.
2539-278 Unable to calloc number of bytes bytes for new hostent h_addr_list array.
Explanation: Out of memory.
User Response: Make adequate memory available.
2539-279 Unable to re-allocate number of bytes bytes for new hostent h_aliases array.
Explanation: Out of memory.
User Response: Make adequate memory available.
2539-280 Unable to malloc number of bytes bytes for interface address array.
Explanation: Out of memory.
User Response: Make adequate memory available.
2539-281 A NULL pointer to the machine stanzas was received in LlConfig::read.
Explanation: Internal LoadLeveler error.
User Response: If problem persists after reconfiguring LoadLeveler, contact IBM Service.
2539-282 A NULL pointer to the default machine stanza was recieved in LlConfig::read.
Explanation: Internal LoadLeveler error.
User Response: If problem persists after reconfiguring LoadLeveler, contact IBM Service.
2539-283 Could not obtain enum value for machine in LlConfig::read.
Explanation: Internal LoadLeveler error.
User Response: If problem persists after reconfiguring LoadLeveler, contact IBM Service.
2539-284 Could not create a default_value LlMachine object in LlConfig::read.
Explanation: Internal LoadLeveler error.
User Response: If problem persists, contact IBM Service.
2539-285 Could not instantiate a Machine object for the host machine in LlConfig::read.
Explanation: Internal LoadLeveler error.
User Response: If problem persists, contact IBM Service.
2539-286 Could not instantiate a Machine object for machine name in LlConfig::read.
Explanation: Internal LoadLeveler error.
User Response: If problem persists, contact IBM Service.
2539-287 The value pool_list value is invalid for pool_list in the machine name machine stanza. Ignored.
Explanation: Invalid value.
User Response: Ensure correctnesss of LoadL_admin stanzas.
2539-288 The negative number pool_list value found in pool_list of the machine name machine_stanza is not allowed. Ignored.
Explanation: Invalid value.
User Response: Do not use negative numbers in a machine pool list.
2539-289 Could not locate the offical host name for machine machine name in LlConfig::read.
Explanation: Internal LoadLeveler error.
User Response: If problem persists, contact IBM Service.
2539-290 Feature statement with number of characters characters exceeds limit of 1024.
Explanation: Feature statement in configuration file is too long.
User Response: Do not ecxceed 1024 bytes in configuration file feature lines.
2539-291 Feature values are not set.
Explanation: Feature values will not take effect due to syntax errors.
User Response: See previously issued error message for explanation.
2539-292 Class statement with number of characters characters exceeds limit of 1024.
Explanation: Class statement too long.
User Response: Do not specify class stanzas that exceed 1024 bytes in length.
2539-293 Default No_Class assumed.
Explanation: A default class value of No_Class will be used.
User Response: See previously issued error message for explanation.
2539-294 Attention: Invalid format found for class statement. Missing braces.
Explanation: Bad class statement syntax.
User Response: Refer to documentation for correct syntax.
2539-295 Attention: Invalid format found for class statement. Missing double qoutes.
Explanation: Bad class statement syntax.
User Response: Refer to documentation for correct syntax.
2539-296 Could not obtain an enum value for stanza type in LlConfig::read.
Explanation: Internal LoadLeveler error.
User Response: Contact IBM Service if problem persists.
2539-297 Could not instantiate a default stanza name object in LlConfig::read.
Explanation: Internal LoadLeveler error.
User Response: Contact IBM Service if problem persists.
2539-298 Could not instantiate a stanza type object for stanza name in LlConfig::read.
Explanation: Internal LoadLeveler error.
User Response: If problem persists, contact IBM Service.
2539-299 A value of value was specified for max_adapter_window in the stanza name stanza.Valid values are 1 - 4 inclusive. Default value of 4 will be used.
Explanation: Default value to be used in place of user-supplied value.
User Response: Refer to documentation for proper value ranges.
2539-300 An adapter stanza name of adapter stanza name was specified in the machine stanza name machine stanza, but an adapter stanza with that name does not exist.
Explanation: A non-existant adapter stanza was referenced in a machine stanza.
User Response: Refer only to existing adapter stanzas in machine stanzas.
2539-301 Could not instantiate a stanza type object in LlConfig::read.
Explanation: Internal LoadLeveler error.
User Response: If problem persists, contact IBM Service.
2539-302 Attention: A value for both SCHEDULER_TYPE and SCHEDULER_API has been specified. SCHEDULER_TYPE will be used.
Explanation: Two conflicting keywords were used.
User Response: Only use SCHEDULER_TYPE in the configuration file.
2539-303 DCE_AUTHENTICATION is not valid. DCE authentication will not be transmitted with job.
Explanation: Invalid keyword was used.
User Response: Do not specify DCE_AUTHENTICATION.
2539-304 The configuration keyword keyword name contains the invalid value keyword value . The default value will be used instead.
Explanation: Invalid keyword value specified.
User Response: Refer to documentation for correct values.
2539-305 More than one stanza identified as stanza name has been found. The first stanza in the LoadL_admin file will be used. All others having the same name will be ignored.
Explanation: Duplicate stanzas were specified in the LoadL_admin file.
User Response: Make sure all LoadL_admin stanzas have unique names.
2539-306 keyword specified in default stanza type stanza. Ignored.
Explanation: The identified keyword should not be specified in the default stanza.
User Response: Refer to documentation for LoadL_admin stanza syntax.
2539-307 Attention: Unknown keyword keyword in stanza type stanza stanza name. Ignored.
Explanation: An unknown keyword was found in the identified stanza.
User Response: Refer to documentation for LoadL_admin stanza syntax.
2539-308 Attention: Invalid value entered for spacct_excluse_enable for machine stanza machine name . Default value will be used.
Explanation: Invalied value entered for spacct_excluse_enable for indicated machine stanza.
User Response: Refer to documentation for correct values.
2539-309 Attention: Value missing for keyword keyword in stanza type stanza.
Explanation: A stanza was defined without the identified keyword.
User Response: Ignore this message if you do not wish to define the associated keyword for this stanza, otherwise, add the keyword and reconfigure LoadLeveler.
2539-310 Attention: Invalid value for keyword in LoadL_admin file: keyword value
Explanation: An invalid value was specified for the identified keyword.
User Response: Refer to documentation for correct values.
2539-311 RESERVED KEYWORD USED: The reserved keyword keyword has been used as a class name. LoadLeveler may not function properly with this reserved keyword used as a class name.
Explanation: A LoadLeveler reserved keyword was used as the name of a job class.
User Response: Refer to documentation for a list of reserved keywords and verify that no job classes use reserved keywords as names.
2539-312 Attention: A value for keyword keyword is required for stanza stanza name . Stanza is ignored.
Explanation: A required keyword is missing from the identified stanza.
User Response: Add required keyword to stanza and reconfigure LoadLeveler.
2539-313 Attention: A css adapter was specified for adapter: adapter stanza name but no switch_node_number was found. Default value will be used.
Explanation: No switch_node_number was associated with the identified adapter stanza. Default will be used.
User Response: Specify switch_node_number for the identified adapter stanza if you do not want the default to be used.
2539-314 Duplicate central manager specified. Stanza for machine machine name will be ignored.
Explanation: The identified machine was defined as a duplicate central manager.
User Response: Only define one machine stanza with "central_manager = yes" in the LoadL_admin file.
2539-315 RM_HOST ignored for machine stanza machine name .
Explanation: Obsolete keyword rm_host was used in a machine stanza.
User Response: Do not use the rm_host keyword any longer. Refer to the documentation for update information about parallel job scheduling.
2539-316 Attention: The keyword adapter_stanzas is used but no value is specified in stanza machine name.
Explanation: The keyword was specified with no value.
User Response: Specify an appropriate value for the keyword or remove the keyword... and then reconfigure LoadLeveler.
2539-317 Cannot specify submit_only for a central manager.
Explanation: The submit_only keyword was set to true for a central manager machine.
User Response: Do not define a primary or alternate central manager as a submit-only machine.
2539-318 Alias specified in default machine stanza. Ignored.
Explanation: An alias was defined for the default machine stanza.
User Response: Only define aliases for stanzas that are associated with real machines.
2539-319 central_manager specified in default machine stanza. Ignored.
Explanation: The default machine stanza was defined as a central manager.
User Response: Only define real machines as cetnral managers.
2539-320 No central manager defined in LoadL_admin machine list.
Explanation: The primary central manager has not been defined for this cluster.
User Response: Define one primary central manager for your LoadLeveler cluster. This is the only required field in the LoadL_admin file.
2539-321 resource limit name resource limit has a value that is too long: value
Explanation: The identified resource limit has a syntax error.
User Response: Refer to documentation for correct resource limit values.
2539-322 Invalid stanza stanza name. Ignored.
Explanation: The identified stanza has an invalid type.
User Response: Refer to documentation for correct LoadL_admin stanza types.
2539-323 Unable to obtain resource limit name resource limit.
Explanation: A system error was returned by the AIX subroutine getrlimit for the indicated resource limit.
User Response: Make sure the resource limit name is correct. If the name is correct, report the machine issuing the error to IBM Service.
2539-324 Unable to create central manager list, no machine list provided.
Explanation: A list of central manager cannot be created because no machine stanzas exist in the LoadL_admin file.
User Response: Define at least one machine as the primary central manager in the LoadL_admin file.
2539-325 Unable to find a central manager in the LoadL_admin file.
Explanation: Unable to find a central manager machine stanza in the LoadL_admin file.
User Response: Define at least one machine as the primary central manager in the LoadL_admin file.
2539-381 Unable to malloc num bytes for DCE credentials file.
Explanation: Unable to allocate memory
User Response: Free up memory on local host.
2539-382 Cannot read filename. Cannot fetch DCE security credentials.
Explanation: Unable to read DCE credentials file.
User Response: Make sure permissions on credentials cache and files are adequate.
2539-383 Cannot open filename. Cannot fetch DCE security credentials.
Explanation: Unable to open DCE credentials file.
User Response: Make sure permissions on credentials cache and files are adequate.
2539-384 Cannot open directory directory_name. Cannot fetch DCE security credentials.
Explanation: Unable to open directory containing DCE credentials files.
User Response: Make sure permissions on credentials the specified directory are adequate.
2539-385 No DCE files with prefix file_prefix were found in sub-directory directory_name.
Explanation: No DCE credentials files were found.
User Response: Ensure DCE credentials are obtained before invoking llsubmit.
2539-386 Unable to malloc num bytes for opaque object.
Explanation: Unable to allocate memory
User Response: Free up memory on local host.
2539-387 Unable to create opaque credentials object.
Explanation: Unable to martial DCE credentials into xdr format.
User Response: This problem requires the attention of an administrator.
2539-388 DCE_AUTHENTICATION_PAIR keyword is not valid.
Explanation: An invalid keyword was entered.
User Response: Correct keyword in LoadLeveler configuration file.
2539-389 Cannot spawn new GetDce Process. errno - error_num.
Explanation: Unable to fork and exec process (llgetdce) to fetch DCE credentials.
User Response: This problem requires the attention of an administrator.
2539-390 Unable to read length of opaque object from process pipe, read returned return_code.
Explanation: The opaque object contains the DCE credentials fetched by the llgetdce process.
User Response: This problem requires the attention of an administrator.
2539-391 Unable to malloc num bytes for opaque object.
Explanation: Unable to allocate memory
User Response: Free up memory on local host.
2539-392 Unable to read opaque object from process pipe, read returned return_code.
Explanation: The opaque object contains the DCE credentials fetched by the llgetdce process.
User Response: This problem requires the attention of an administrator.
2539-393 Unable to read stderr from child, read returned return_code.
Explanation: The failure occured when LoadLeveler tried to read from the stderr pipe to get to the llgetdce process.
User Response: This problem requires the attention of an administrator.
2539-394 Failed to write size of opaque object (object_size) to stdout, errno = error_num.
Explanation: The opaque object contains the DCE credentials fetched by the llgetdce process.
User Response: This problem requires the attention of an administrator.
2539-395 Failed to write opaque object to stdout, errno = error_num.
Explanation: The opaque object contains the DCE credentials fetched by the llgetdce process.
User Response: This problem requires the attention of an administrator.
2539-416 User failed username security validation. Username did not match expected name, expected username .
Explanation: User name did not match primary LoadLeveler user name (for example, "loadl").
User Response: Ensure that /etc/LoadL.cfg contains the same LoadLeveler user name for all machines in the cluster.
2539-417 Cannot receive hostname from client.
Explanation: Error receiving hostname from connecting host.
User Response: Internal LoadLeveler routing error. If problem persists, recycle LoadLeveler daemons.
2539-418 Cannot send hostname.
Explanation: Error sending hostname to another host.
User Response: Internal LoadLeveler routing error. If problem persists, recycle LoadLeveler daemons.
2539-419 Attention: Host name returned by validate_connection (validate_connection host name) does not match caller host name (caller host name)
Explanation: Name service returned a different name for this host than the name that was expected.
User Response: No action - this is an attention message.
2539-420 Connection from hostname rejected; not in machine list.
Explanation: Host failed validation because MACHINE_AUTHENTICATE = TRUE and host is not in LoadL_admin machine list.
User Response: Add host to LoadL_admin machine list if you want it to participate in the LoadLeveler cluster.
2539-421 Cannot receive remote host name (IP address port port number) errno = error num
Explanation: gethostbyaddr() failed for IP address.
User Response: Set MACHINE_AUTHENTICATE to false to allow all hosts to participate, or check validity of IP address.
2539-422 ProtocolReset: Cannot send protocol version.
Explanation: Error sending daemon protocol version.
User Response: Internal LoadLeveler routing error. If problem persists, recycle LoadLeveler daemons.
2539-423 ProtocolReset: Cannot send machine name.
Explanation: Error sending host name.
User Response: Internal LoadLeveler routing error. If problem persists, recycle LoadLeveler daemons.
2539-424 Cannot send step job step name.
Explanation: Error sending job step information.
User Response: Internal LoadLeveler routing error. If problem persists, recycle LoadLeveler daemons.
2539-425 Cannot send end of record for step job step name.
Explanation: Error sending transaction end-of-record marker.
User Response: Internal LoadLeveler routing error. If problem persists, recycle LoadLeveler daemons.
2539-426 Cannot send step id job step name.
Explanation: Error sending job step id.
User Response: Internal LoadLeveler routing error. If problem persists, recycle LoadLeveler daemons.
2539-427 Error receiving acknowledgement for step job step name.
Explanation: Error receiving transaction acknowledgement for a job step.
User Response: Internal LoadLeveler routing error. If problem persists, recycle LoadLeveler daemons.
2539-428 ProtocolReset: Cannot receive protocol version.
Explanation: Cannot receive protocal version from connecting machine.
User Response: Internal LoadLeveler routing error. If problem persists, recycle LoadLeveler daemons.
2539-429 ProtocolReset: Cannot receive machine name.
Explanation: Cannot receive name of connecting machine.
User Response: Internal LoadLeveler routing error. If problem persists, recycle LoadLeveler daemons.
2539-430 Attention: Routing default machine.
Explanation: Routing an entire machine object rather than transaction-specific machine data.
User Response: Attention message: no action required.
2539-431 Unrecognized specification: specification name (specification value)
Explanation: Erroneous machine data encountered.
User Response: Internal LoadLeveler routing error. If problem persists, recycle LoadLeveler daemons.
2539-432 Invalid value defined in the stanza type stanza stanza name for keyword = value.
Explanation: Invalid value defined for keyword in the named stanza.
User Response: Validate correctness of stanzas in LoadL_admin file.
2539-433 Invalid keyword keyword specified in the staza type stanza stanza name.
Explanation: Invalid keyword defined in the named stanza.
User Response: Validate correctness of stanzas in LoadL_admin file.
2539-434 The keyword keyword specified in the stanza type stanza stanza name cannot be NULL.
Explanation: A keyword was specified with a NULL value in the named stanza.
User Response: Validate correctness of stanzas in LoadL_admin file.
2539-435 Cannot append to keyword in the stanza name stanza type stanza.
Explanation: Error appending a value to a keyword in the named stanza.
User Response: Ensure you are not treating a non-list stanza keyword as a list type.
2539-436 Cannot find central manager. Unable to queue command (command number) to central manager.
Explanation: Central manager machine could not be found in this daemon's configuration.
User Response: Make sure the central manager is defined in the LoadL_admin file and that it, or an alternate, is running.
2539-437 No log directory specified in the LoadL_config file for this daemon.
Explanation: No log directory specified in the LoadL_config file for this daemon.
User Response: Specify a log file for this daemon in the LoadL_config file, and reconfigure.
2539-438 Attention: Cannot chdir to directory name. Attempting to continue...
Explanation: Unable to change to the log directory.
User Response: Check existence and permissions of directory.
2539-439 No spool directory specified in the LoadL_config file.
Explanation: Path for the local spool directory was not specified in the LoadL_config file.
User Response: Add a path for the local spool directory to the LoadL_config file and reconfigure or restart daemons.
2539-440 No execute directory specified in the LoadL_config file.
Explanation: Path for the local execute directory was not specified in the LoadL_config file.
User Response: d a path for the local execute directory to the LoadL_config file and reconfigure or restart daemons.
2539-441 Attention: Cannot set userid to uid number(user name). Attempting to continue...
Explanation: Error setting effective userid.
User Response: Make sure daemon runs as root, and check validity of uid.
2539-442 Attention: Cannot set groupid to gid number(group name). Attempting to continue...
Explanation: Error setting effective groupid.
User Response: Make sure daemon runs as root, and check validity of gid.
2539-443 No history file specified in the LoadL_config file.
Explanation: No history file specified in the LoadL_config file.
User Response: Add history file to LoadL_config and reconfigure or restart daemons.
2539-444 Attention: Value specified for cm_heartbeat_interval is invalid. Default value (= default cm_heartbeat_interval value) will be used.
Explanation: Value specified for cm_heartbeat_interval is invalid.
User Response: Refer to LoadLeveler documentation for correct cm_heartbeat_interval settings.
2539-445 Attention: Value specified for cm_timeout is invalid. Default value (default cm_timeout value) will be used.
Explanation: Value specified for cm_timeout is invalid.
User Response: Refer to LoadLeveler documentation for correct cm_timeout settings.
2539-446 No central manager defined. Cannot continue.
Explanation: No central manager defined in the LoadL_admin file.
User Response: Define a central manager in the LoadL_admin file and restart LoadLeveler.
2539-447 LlNetProcess: Unable to instantiate LlConfig object.
Explanation: Unable to allocate internal LoadLeveler data structure.
User Response: Ensure sufficient memory is available on machine. Save logs and contact IBM Service if problem persists.
2539-448 Syntax error in LoadLeveler configuration files.
Explanation: Syntax error in config file.
User Response: Check syntax of LoadL_config and LoadL_admin files.
2539-449 Unable to instantiate this_machine object.
Explanation: Unable to allocate internal LoadLeveler data structure.
User Response: Ensure sufficient memory is available on machine. Save logs and contact IBM Service if problem persists.
2539-450 Unable to instantiate this_cluster object.
Explanation: Ensure sufficient memory is available on machine.
User Response: Save logs and contact IBM Service if problem persists.
2539-451 Attention: No administrator list specified in LoadL_config file.
Explanation: No administrator list specified in LoadL_config file.
User Response: Specify an administrator list in the LoadL_config file in order for administrative functions to be enabled.
2539-452 daemon name is orphaned! Exiting...
Explanation: Daemon is no longer a child of the LoadL_master daemon.
User Response: Check logs to diagnose problem, or simply restart LoadLeveler.
2539-453 Illegal protocol (sender process' protocol version), received from another process on this machine - machine name. This daemon daemon name is running protocol version (version).
Explanation: Two daemons on this machine have different protocol versions. Run "llctl -v" to verify daemon and command versions.
User Response: Run "llctl -v" to verify daemon and command versions. Contact LoadLeveler administrator if a software upgrade is needed.
2539-454 Illegal protocol (protocol version of sending machine), received from name of sending machine. This machine receiving machine is running protocol version (version).
Explanation: LoadLeveler daemons on two different machines are at different protocol levels.
User Response: Run "llctl -v" to verify daemon and command versions on all machines. Contact LoadLeveler administrator if a software upgrade is needed.
2539-455 Attention: Allocating base Machine object.
Explanation: LoadLeveler is allocating a generic machine, not a LoadLeveler-defined machine.
User Response: Internal LoadLeveler condition. If problem persists, contact IBM Service.
2539-456 Cannot allocate Machine object for new machine: machine name
Explanation: Memory allocation error.
User Response: Ensure adequate memory is available on machine where error occurs.
2539-457 Cannot gethostbyname for machine: machine name
Explanation: gethostbyname() routine returned an error for named machine.
User Response: Ensure that machine exists and that the name being used is resolvable. Verify that LoadL_admin contains valid machine names.
2539-458 Unable to find or allocate Machine object for machine(machine name or IP address).
Explanation: Internal LoadLeveler trying to locate data for the named machine.
User Response: Ensure adequate memory is available on machine where error occurs. Verify that LoadL_admin contains valid machine names.
2539-459 Cannot gethostbyaddr for machine: machine name
Explanation: gethostbyaddr() routine returned an error for named machine.
User Response: Ensure that machine exists and that the address being used is resolvable. Verify that LoadL_admin contains valid machine names.
2539-460 Cannot start thread for service service type on port port number. rc = return code
Explanation: Error creating LoadLeveler thread.
User Response: Ensure sufficient memory is available and recycle LoadLeveler. If problem persists, contact IBM Service.
2539-461 Attention: Connection to machine name port port number reset. Retrying...
Explanation: Attempting to reconnect to named machine via indicated port.
User Response: Attention message - no action.
2539-462 Attention: Connection to machine name path socket path reset. Retrying...
Explanation: Attempting to reconnect to named machine via indicated socket path.
User Response: Attention message - no action.
2539-463 Cannot connect to machine name service name on port port number. errno = errno
Explanation: Error connecting to named service on named machine and port.
User Response: Check errno value and take appropriate action.
2539-464 Cannot connect to machine name path socket path. errno = errno.
Explanation: Error connecting to named machine via indicated socket path.
User Response: Check errno value and take appropriate action.
2539-465 sendFile: Cannot get file size. errno = errno
Explanation: Error performing internal LoadLeveler file operation.
User Response: Use errno value to attempt to identify problem. Call IBM Service if problem persists.
2539-466 sendFile: Cannot send file size. errno = errno.
Explanation: Error performing internal LoadLeveler file operation.
User Response: Use errno value to attempt to identify problem. Call IBM Service if problem persists.
2539-467 sendFile: Cannot flush file size. errno = errno
Explanation: Error performing internal LoadLeveler file operation.
User Response: Use errno value to attempt to identify problem. Call IBM Service if problem persists.
2539-468 sendFile: Cannot read ready-to-receive. errno = errno
Explanation: Error performing internal LoadLeveler file operation.
User Response: Use errno value to attempt to identify problem. Call IBM Service if problem persists.
2539-469 sendFile: Requestor refuses file.
Explanation: Error performing internal LoadLeveler file operation.
User Response: Call IBM Service if problem persists.
2539-470 sendFile: Cannot flush file. errno = errno
Explanation: Error performing internal LoadLeveler file operation.
User Response: Use errno value to attempt to identify problem. Call IBM Service if problem persists.
2539-471 sendFile: No FileDesc specified.
Explanation: Error performing internal LoadLeveler file operation.
User Response: If the problem persists, contact IBM service.
2539-472 receiveFile: Cannot receive file size. errno = errno.
Explanation: Error performing internal LoadLeveler file operation.
User Response: Use errno value to attempt to identify problem. Call IBM Service if problem persists.
2539-473 receiveFile: Cannot send status. errno = errno.
Explanation: Error performing internal LoadLeveler file operation.
User Response: Use errno value to attempt to identify problem. Call IBM Service if problem persists.
2539-474 receiveFile: Cannot flush file size. errno = errno
Explanation: Error performing internal LoadLeveler file operation.
User Response: Use errno value to attempt to identify problem. Call IBM Service if problem persists.
2539-475 Cannot receive command from client machine name, errno =errno.
Explanation: Internal LoadLeveler transaction error.
User Response: Recycle daemons if problem persists. Call IBM Service if recycling daemons does not alleviate problem.
2539-476 Got unknown command (command value)
Explanation: Internal LoadLeveler transaction error.
User Response: Recycle daemons if problem persists. Call IBM Service if recycling daemons does not alleviate problem.
2539-477 Cannot fork child process. errno = errno
Explanation: Error forking child process.
User Response: Use errno value to diagnose problem.
2539-478 Cannot change process group. errno = errno
Explanation: Error changing process group.
User Response: Use errno value to diagnose problem.
2539-479 Cannot listen on port port number for service service name.
Explanation: Error listening on port for named service.
User Response: Check to see if named service is already running on machine. Check to see if port is in use.
2539-480 Cannot start main socket. errno = errno
Explanation: Error starting socket.
User Response: User errno value to diagnose problem.
2539-481 Cannot start new TransAction thread. rc = return code
Explanation: Error creating LoadLeveler Transaction thread.
User Response: Ensure sufficient memory is available and recycle LoadLeveler. If problem persists, contact IBM Service.
2539-482 Cannot start new Stream Connection thread. rc = return code.
Explanation: Error creating LoadLeveler Stream thread.
User Response: Ensure sufficient memory is available and recycle LoadLeveler. If problem persists, contact IBM Service.
2539-483 Cannot perform chmod on input socket socket path. errno = errno
Explanation: Error changing permissions on socket path.
User Response: Check existence of socket path and authentication of process attempting chmod.
2539-484 Cannot start unix socket on path socket path. errno = errno
Explanation: Error starting UNIX socket.
User Response: Use errno value to diagnose problem.
2539-485 Cannot start new Unix Connection thread. rc = return code.
Explanation: Error starting LoadLeveler UNIX Connection thread.
User Response: Ensure sufficient memory is available and recycle LoadLeveler. If problem persists, contact IBM Service.
2539-486 Cannot start new datagram Connection thread. rc = return code.
Explanation: Error starting LoadLeveler datagram Connection thread.
User Response: Ensure sufficient memory is available and recycle LoadLeveler. If problem persists, contact IBM Service.
2539-488 The daemon name daemon must be run as root.
Explanation: The named daemon can only be run by the root user.
User Response: su to root and run daemon.
2539-489 Unable to open /dev/null (errno = errno) to re-direct stdin. Continuing.
Explanation: Daemon creation error.
User Response: Use errno to diagnose problem.
2539-490 Unable to open /dev/null (errno = errno) to re-direct stdout. Continuing.
Explanation: Daemon creation error.
User Response: Use errno to diagnose problem.
2539-491 Cannot start main thread. rc = return code
Explanation: Error initializing main daemon thread.
User Response: Ensure sufficient memory is available and recycle LoadLeveler. If problem persists, contact IBM Service.
2539-492 Unable to set_user_euid(uid number)
Explanation: Failure to set effective user id.
User Response: Check setuid permissions of daemon binary file.
2539-493 Unable to set_user_ruid(uid number)
Explanation: Failure to set real user id.
User Response: Contact LoadLeveler administrator if problem persists.
2539-494 Unable to chdir to /tmp: strerr error text
Explanation: Error changing to /tmp directory.
User Response: Use strerr() output to diagnose problem.
2539-566 Failed to route field (specification code) in location
Explanation: An error occurred attempting to route between daemons. The problem may be a network or TCP problem or may be an internal LoadLeveler problem.
User Response: If problem persists, contact IBM Support.
2539-567 object fetch function does not recognize specification field(specification code)
Explanation: A field was requested from an object but the field identifier is not known by the object. This is an internal LoadLeveler error.
User Response: If problem persists, contact IBM Support.
2539-568 function name is returning a NULL element for specification specification name (specification value)
Explanation: An unexpected NULL value is being returned for a specification. (Internal LoadLeveler Error).
User Response: If problem persists, contact IBM Support.
2539-591 internal context (specification number) not recognized by fetch()
Explanation: Unrecognized data type.
User Response: Call IBM Service.
2539-592 internal context (specification number) not recognized by insert()
Explanation: Unrecognized data type.
User Response: Call IBM Service.
2539-593 Cannot rename file name to new file name. Logging may be incomplete. errno = errno
Explanation: Cannot rename a file to file name with .old extension.
User Response: Check filesystem space and permissions.
2539-594 Cannot open input file file name for copy, errno = errno.
Explanation: Cannot open file for input.
User Response: Check existence and permissions of file.
2539-595 Cannot open log file file name, errno = errno. Logging will go to stderr.
Explanation: Cannot open log file. Check file existence and permissions.
User Response:
2539-596 No name specified for log file. Logging will go to stderr.
Explanation: No log file name was specified in LoadLeveler configuration files for this daemon.
User Response:
2539-597 Error non-translated error line source line number file file name.
Explanation: Non-translated source code error message.
User Response: Report this error to IBM Service.
2539-598 Job job number. step number - ERROR, usage_info has not been initialized.
Explanation: Error recording job usage information.
User Response: Drain and then recycle LoadL_startd daemon.
2539-599 Job job number.step number - Unable to malloc number of bytes bytes for a MACH_USAGE struct
Explanation: Error allocating memory.
User Response: Make memory available on host machine.
2539-600 Unable to create string for copy of file name.
Explanation: Memory allocation error.
User Response: Ensure sufficient memory is available on host machine.
2539-601 Incorrect status file name - file name.
Explanation: Status file name error.
User Response: Drain LoadLeveler on host machine and recycle daemons.
2539-602 status file, file name, already exists
Explanation: Status file already exists.
User Response: none
2539-603 Cannot create status file, file name, errno = errno error message.
Explanation: Cannot create file.
User Response: Check file permissions and path and filesystem space.
2539-604 Cannot open status file, file name, errno = errno [error message.
Explanation: Cannot open file.
User Response: Check file permissions and path and filesystem space.
2539-605 Cannot remove status file, file name, errno = error number error message.
Explanation: Error deleting file.
User Response: Check file path and permissions.
2539-606 Cannot write number bytes to status file, filename, errno = errno error message.
Explanation: Error writing to file.
User Response: Check file path and permissions and filesystem space.
2539-607 lseek failed for status file, file name, offset = file offset, whence = offset usage flag, errno = errno error message.
Explanation: Failure to set file pointer.
User Response: Check file path and permissions.
2539-608 Cannot remove usage file, file name, errno = errno error message.
Explanation: Error trying to delete file.
User Response: Check file path name and permissions.
2539-609 Cannot open usage file filename to read. errno = error num.
Explanation: Cannot open file.
User Response: Check file path name and permissions and available filesystem space.
2539-610 Cannot route dispatch usage for file filename.
Explanation: Cannot send file to peer daemon.
User Response: Ensure LoadLeveler is running on all involved machines.
2539-611 Cannot open usage file filename to write. errno = error num
Explanation: Cannot open file.
User Response: Check file path name and permissions.
2539-612 Cannot write dispatch usage file filename.
Explanation: Cannot write to file.
User Response: Check file path name and permissions.
2539-751 getrlimit or setrlimit for resource name limit failed. errno=errno error msg.
Explanation: The getrlimit or setrlimit system call failed.
User Response: Correct the problem indicated by the error number.
2539-752 The system call name system call failed for user username. errno=error num error msg.
Explanation: The specified system call failed.
User Response: Correct the problem indicated by the error number.
2539-753 The uid for user, user name, on the executing machine (uid) does not match uid on submitting machine (uid).
Explanation: The user must have the same uid on both the submitting and executing machines.
User Response: Configure LoadLeveler to allow user to only run on machines with the same uid or change uids on machines in the LoadLeveler cluster.
2539-754 The gid (gid) for user, user name, on the submitting machine was not found in the group list for the user on the executing machine.
Explanation: The user's group id on the submitting machine must be a valid group for the user on the executing machine.
User Response: Configure LoadLeveler to allow user to only run on machines where the gid is valid or change add the gid to the user's group list on all machines in the LoadLeveler cluster.
2539-755 The system call to set the real or effective uid to uid failed. errno=error num error msg.
Explanation: The specified system call failed.
User Response: Correct the problem indicated by the error number.
2539-756 The setregid systen call failed for gid gid. errno=error num error msg.
Explanation: The setregid system call failed.
User Response: Correct the problem indicated by the error number.
2539-757 object ID does not have a StepVars object.
Explanation: The object was asked for its global keyword value structure but one does not exist. The object can be a Job, Step or StepList.
User Response: Report the error to the LoadLeveler administrator. Verify that the Job in the source file is correct.
2539-758 object ID does not have a TaskVars object.
Explanation: The object was asked for its global keyword value structure but one does not exist. The object can be a Job, Step, StepList, Node, Task or TaskInstance.
User Response: Report the error to the LoadLeveler administrator. Verify that the Job in the source file is correct.
2539-759 object type object num is not contained and cannot return StepVars.
Explanation: The object was asked for its global keyword value structure but does not keep one locally and is not contained by an object that does (eg. A node would return the StepVars of the Step that contains it).
User Response: Report the error to the LoadLeveler administrator. Verify that the Job in the source file is correct.
2539-760 Attempt to reassign Task instances to Step step name.
Explanation: An attempt was made to create the task instances for a Step after machine assignements were made but the Step was found to already have task instances. This indicates a corruption of the LoadLeveler process.
User Response: Report the error to the LoadLeveler administrator.
2539-761 object type object num is not contained and cannot return TaskVars.
Explanation: The object was asked for its global keyword value structure but does not keep one locally and is not contained by an object that does (eg. A task instance would return the TaskVars of the task that contains it).
User Response: Report the error to the LoadLeveler administrator. Verify that the Job in the source file is correct.
2539-762 Failed to set AFS credentials. errno=error num error msg.
Explanation: A failure occured trying to establish AFS token(s).
User Response: Verify that AFS is installed on executing machine. Verify that llafs.shr.o exists in the same directory which contains LoadL_master.
2539-763 Unable to set dce security credentials. Job will proceed without dce credentials. errno=error num error msg.
Explanation: A failure occured trying to establish DCE credentials.
User Response: Verify that DCE is installed on executing machine. Verify that executables specified in DCE_AUTHENTICATION_PAIR exist. Use errno to help identify the cause of the problem.
2539-764 Unable to import DCE context. Will continue without credentials. errno=error num error msg.
Explanation: Unable to import DCE credentials returned by the llsetdce executable.
User Response: Verify that llsetdce, or its replacement, exists and matches the interface for a LoadLeveler dce authentication exit.
2539-765 Unable to remove DCE credentials.
Explanation: LoadLeveler was unable to remove DCE credentials.
User Response: Monitor the DCE credential cache to see if excess credentials are being left by LoadLeveler.
2539-766 Unable to fetch DCE credentials. DCE credentials will not be included in job submission.
Explanation: Self explanatory.
User Response: Verify that DCE is installed and that the DCE_AUTHENTICATION_PAIR keyword is set correctly in the configuration file.
2539-767 STARTER not specified in config file.
Explanation: Self explanatory.
User Response: Verify that the STARTER keyword is correctly specified in the configuration file.
2539-768 Unable to open database for job queue job queue because: errno=error code (error description)
Explanation: The job queue file could not be opened. The additional information specifies why.
User Response: Correct the problem as indicated by the message and errno.
2539-769 function name: Error retrieving Job StepList from Queue. Unable to route step type.
Explanation: The job in the job queue has been corrupted and could not be retrieved.
User Response: Contact the LoadLeveler administrator.
2539-770 function name: Error retrieving Job Steps from Queue. object type (encoding of object) is not a valid type.
Explanation: The job in the job queue has been corrupted and could not be retrieved.
User Response: Contact the LoadLeveler administrator.
2539-771 Invalid data type= data type in function name.
Explanation: Internal error.
User Response: Contact the LoadLeveler administrator.
2544-850 Cannot allocate storage for array of machines.
Explanation: The program could not allocate virtual memory.
User Response: Verify that the machine has a reasonable amount of virtual memory available for the LoadLeveler processes. If problem persists, contact IBM service.
2544-851 Wall_clock_limit not specified, but is required when using Backfill scheduler.
Explanation: No value could be found in the job command file or in the admin file for wall_clock_limit. This limit must be specified when using the BACKFILL scheduler. The job step will not be run.
User Response: Specify a value for this limit in either the job command file you are submitting, or in the admin file. Refer to Using and Administering LoadLeveler for more information on wall_clock_limit.
2544-852 The default scheduler does not support multiple tasks per node.
Explanation: The default LoadLeveler scheduler does not support scheduling of multiple tasks on a node, but this has been requested in the submitted job. The job step will not be run.
User Response: Use the Backfill (or some other) scheduler that supports multiple tasks per node. Refer to Using and Administering LoadLeveler for more information on the scheduler_type keyword in the configuration file.
2544-853 The default scheduler does not support multiple adapter requirements.
Explanation: The default LoadLeveler scheduler does not support multiple adapter requirements specified in multiple network statements in the job just submitted. The job step will not be run.
User Response: Use the Backfill (or some other) scheduler that supports multiple adapter requests. Refer to Using and Administering LoadLeveler for more information on the scheduler_type keyword in the configuration file.
2544-854 The default scheduler does not support interactive jobsteps.
Explanation: The default LoadLeveler scheduler does not support the scheduling of interactive jobsteps. The job step will not be run.
User Response: Use the Backfill (or some other) scheduler that supports interactive job steps. Refer to Using and Administering LoadLeveler for more information on the scheduler_type keyword in the configuration file.
2544-855 Class class name with number of defined initiators initiators defined and number of used initiators currently in use is too busy to run Step step id requiring number of initiators initiators.
Explanation: Step could not be scheduled because there were not enough free initiators available.
User Response: Increase the number of initiators, or wait until some jobsteps of this class complete, and resubmit the job.
2544-856 User user name running number of steps steps with maximum of max number of steps when Step step id is being considered.
Explanation: The user has reached the maximum number of steps that can be run as coded in the maxjobs keyword in the user stanza in the admin file. The jobstep will not be run.
User Response: The user can wait until some of the his jobs complete, or the administrator can increase the value for the maxjobs keyword.
2544-857 Group group name running number of steps steps with maximum of maximum steps when Step step id is being considered.
Explanation: The group has reached the maximum number of steps that can be run as coded in the maxjobs keyword in the group stanza in the admin file. The step will not be run.
User Response: The user can wait until some of the group's jobs complete, or the administrator can increase the maxjobs keyword.
2544-858 Class class name is busy: steps running= number of steps, max= maximum steps when Step step id is being considered.
Explanation: The class has reached the maximum number of steps that can be run as coded on the maxjobs keyword in the class stanza in the admin file. The step will not be run.
User Response: The user can wait until some of the class's jobs complete, or the administrator can increase the maxjobs keyword.
2544-859 Schedd machine machine name is running number of steps steps with maximum of maximum steps when Step step id is being considered.
Explanation: The schedd has reached the maximum number of steps that can be run as coded on the max_jobs_scheduled keyword in the machine stanza in the admin file.
User Response: The user can wait until some of the schedd's jobs complete, or the administrator can increase the max_jobs_scheduled keyword.
2544-860 Machine machine name in hostlist is not in the cluster when Step step id is being considered.
Explanation: A machine name was found in the hostlist that does not match any known machines in the cluster. The step will not be run.
User Response: Add the machine to the cluster or remove it from the hostlist and resubmit the job.
2544-861 Machine machine name in hostlist is unavailable when Step step id is being considered.
Explanation: A machine name was found in the hostlist that is not currently available. The step will not be run.
User Response: Wait until that machine becomes available, or remove it from the hostlist and resubmit the job.
2544-862 Machine machine name is running steps, Step step id asks for not shared nodes.
Explanation: A machine in the hostlist is already busy running steps, but the step being considered requires not shared nodes. The step will not be run.
User Response: Wait until that machine frees up, or remove it from the hostlist and resubmit the job.
2544-863 Machine machine name is busy running steps and is being used exclusively when Step step id is being considered.
Explanation: A machine in the hostlist is already busy running steps, and has been allocated to another job exclusively. The step will not be run.
User Response: Wait until that machine frees up, or remove it from the hostlist and resubmit the job.
2544-864 Machine machine name is running number of steps steps with max_starters of maximum steps when Step step id is being considered.
Explanation: The machine has reached the maximum number of steps that can be run as coded on the max_starters keyword in the config file. The step will not be run.
User Response: The user can wait until some of the machines's jobs complete, or the administrator can increase the max_starters keyword.
2544-865 Machine machine name in hostlist is not currently allowed to run steps when Step step id is being considered.
Explanation: The machine found is the hostfile is not currently allowed to run jobs as coded in the config file's execution window when the step is being considered. The step will not be run.
User Response: Modify the execution window for the given machine, or remove the machine from the hostlist and try again.
2544-867 Machine machine name does not have free adapter to run the Step step id.
Explanation: The adapter on the machine listed is being currently in use.
User Response: Wait until the jobstep(s) using the adapter complete, and resubmit the job.
2544-868 Step step id cannot be scheduled at this time because it requires resources already reserved for a higher priority step.
Explanation: This step was being considered to be scheduled as a "backfill" candidate, but scheduling this step at this time will interfere with the scheduling of a higher priority step, since resources that this step required hava already been assigned to the higher priority step.
User Response: Try running jobstep again.
2544-869 Step step id was marked "not runnable" at time due to dependency.
Explanation: Step is not runnable because dependency condition evaluated to false.
User Response: Fix or eliminate the failing dependency condition that is prohibiting this jobstep from running.
2544-870 Step step id was not considered to be run in this scheduling cycle due to its relatively low priority or because there are not enough free resources.
Explanation: Step was not considered because higher priority jobs already consumed all the available resources.
User Response: Increase the priority of the jobstep, or wait until higher priority jobsteps complete, and resubmit the job. Verify that you are requesting valid resources (machines, adapters, classes, etc.)