AWSBDW - Jobman messages
This section lists error and warning messages that might be issued by the jobman component.
The message component code is BDW.
AWSBDW001E
Jobman cannot set the process group id to the group id of the logon user. The operating system error is: "system_message".
Internal error: Setgid() failed with the indicated error.
system_message contains the operating system error.
Jobman proceeds.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW002E
The user ID used to launch this job is not valid. The operating system error is: "system_error_number".
To launch a job, a user ID must have the following characteristics:
- It must be a valid user ID for the computer on which the job is launched
- It must be defined in the mozart database with permission to launch jobs.
Further, the user ID must be supplied correctly when the job is launched, either from the command line or from the mozart database.
system_error_number contains the operating system error message.
Internal error: Setuid() failed with the indicated error.
Jobman proceeds.
Follow this procedure:
- Check the job properties in the plan list from the Job Scheduling Console, or use the sj schedid.jobid;L command in conman to obtain the user ID with which HCL Workload Automation is attempting to launch the job.
- Verify that the user ID has been supplied correctly. If not, modify the job definition used to launch the job to identify a different user that has the rights to launch jobs on this workstation.
- If the correct user ID has been supplied, verify that the user ID is defined in the mozart database as a user with the rights to launch jobs. If it is not, you need to either change the user in the job definition to a user that has the rights to launch jobs on this workstation, or define the original user ID to have these rights in the mozart database. Note that only a HCL Workload Automation administrator can do this.
- If the user ID is defined in the mozart database with rights to launch jobs, verify that the user ID is defined in the operating system. If it is not, you need to define the user ID to the operating system, using the operating system's standard procedures for creating a user. Note that you might not have the rights to do this; you might have to log on as Administrator or root.
When you have corrected the problem, either rerun the job using the from option (specifying the same name of the job) or submit the job into the plan.
AWSBDW003E
Jobman cannot change the current working directory to the home directory of the logon user. The operating system error is: "system_error".
Internal error: Chdir() failed with errno = system_error.
system_error is the operating system error message.
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW004E
Jobman could not run the job because the system call used to launch the job failed. The operating system error is: "system_error".
This message was previously: Exec failed with errno = system_error.
system_error is the operating system error message.
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW005E
The JCL file "file_name" could not be launched. The operating system error is: "system_error_number".
system_error_number contains the operating system error message number. file_name is the name of the JCL file HCL Workload Automation is trying to launch.
The program stops.
Verify that the JCL file specified in the job definition is correct, the file exists and it is readable and executable by the HCL Workload Automation user. Rerun or submit an ad-hoc job after the problem has been resolved.
AWSBDW006E
Jobman could not run a job or check an external dependency because an internal system call failed. The error number is: "error_number".
Internal error: Monitor could not fork to create job process. Errno = error_number
error_number is the operating system error number.
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW009E
The following operating system error occurred retrieving the password structure for either the logon user, or the user who owns a file or external dependency: "system_error".
This message is a warning when checking a file dependency or when getting the status of an external dependency.
It is an error when trying to launch a job. Jobman cannot retrieve the password structure from the system for either the logon user, the Check File user (CFuser), or the Get Status user (GSuser).
system_error is the operating system error message.
The logon must be a valid user on the system where the job is being launched or check file or get status is being requested. It has a different meaning according to the platform.
- UNIX: The user logon does not exist.
- Windows: The problem might be caused by a confusion between local or domain accounts; however the logon must be valid and must be correctly associated with the password stored in the Symphony file and the userdata database.
If the user was documented incorrectly in the plan, update the value in the database and use the rerun command with the from option so that HCL Workload Automation can read the original definition or resubmit the job into the plan.
AWSBDW010E
Jobman was unable to create the monitor process that runs and monitors a job. The operating system error is: "system_error".
system_error is the operating system error message.
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW011E
Jobman received unexpected signal !1.
AWSBDW012E
Jobman was unable to delete the following JCL file "file_name" because it cannot find it or does not have the rights to delete it. The operating system error is: "error_message".
file_name is the name of the file jobman is attempting to delete.
error_message is a message that contains more information about the error and includes the operating system error message, if any.
Technical note for support: This is a MPE related problem only.
The program proceeds.
Remove the indicated JCL file manually.
AWSBDW013E
Unable to Launch job !1.
AWSBDW014E
Jobman found a mailbox record in the Courier.msg file in an unrecognizable format, and was unable to process it.
This error happens because either a more recent version of HCL Workload Automation is working within the same network or the event has been corrupted.
The program proceeds.
In the former case, follow the advice about upgrading your installation in the Planning and Installation Guide.
In the latter case, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW016E
Jobman was unable to end the following user job due to a system error: "job_name", #"job_number". The operating system error is: "system_error".
job_name is the name of the job that has not ended. job_number is the number that identifies this job in the process list (PID). system_error contains the operating system error message.
The program proceeds.
Stop the job manually using one of the following:
- UNIX: use the conman kill command.
- Windows: use the Task Manager.
- Either: use the HCL Workload Automation utility killproc in the HCL Workload Automation bin directory.
AWSBDW017E
Jobman cannot create a new session for the monitor daemon. The operating system error is: "system_error".
This is an internal error: Setsid failed with errno = system_error.
Jobman creates a new session as part of the process to create a monitor daemon process. The monitor process is the parent of the process that runs a job.
system_error is the operating system error message
Jobman stops.
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW018E
Timeout on Courier.
AWSBDW020E
Error occurred opening stdin !1.
AWSBDW021E
Error occurred opening stdout !1.
AWSBDW022E
Error occurred opening stderr !1.
AWSBDW023E
A monitor process encountered an error while waiting for its child process to terminate. The operating system error is: "system_error".
Internal error: Jobprocess Wait error: system_error.
Jobman creates a monitor process for each job that it launches. The monitor process starts the job, waits for the job to complete, and reports the job exit status. In normal circumstances the monitor process then terminates. However, in this case it cannot terminate. A monitor process is also used by jobman to monitor the method that checks the status of external dependencies.
system_error is the operating system error message.
Jobman continues, with the monitor process still running.
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
You can attempt to terminate the process yourself, using the options of your operating system. See the job standard list to determine the outcome.
AWSBDW024W
No Writers on Courier (Writers = !1).
AWSBDW026E
The file that jobman is trying to delete was expected to be a JCL file, but is not.
See message.
The program proceeds.
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW028E
Jobman encountered the following incorrect test condition when attempting to check an opens file dependency: "qualifier". The file being checked is the following: "file_name".
file_name is the name of the file specified by the opens dependency.
qualifier is the qualifier specified in the opens dependency.
Make sure that the qualifier specified with the opens dependency is valid. Correct the job description and reschedule or rerun it.
AWSBDW029E
Jobman is trying to end the following job: "job_name", but was unable to find it in the job table.
job_name is the job that cannot be stopped because it is not in the job table.
The program proceeds.
Probably the job has stopped. If it is still running, stop it manually.
Stop the job manually using one of the following:
- UNIX: use the conman kill command.
- Windows: use the Task Manager.
- Either: use the HCL Workload Automation utility killproc in the HCL Workload Automation bin directory.
AWSBDW032E
Jobman is trying to perform an operation as root or Administrator which is not authorized.
Previous message text: Root jobs are not authorized to be executed by TWS.
This error occurs when jobman has to launch a job as root or Administrator and the option jm no root in the localopts file is set to yes. This error also happens when jobman has to launch the command to verify the existence of a file which has been specified in a opens dependency. In the case of an extended agent, this error could also occur if the Cfuser has not been set.
The program proceeds.
Use a user other than root or Administrator.
If this is an extended agent, specify a user for the extended agent's jobs which is in the extended agent's configuration files.
Evaluate the possibility to change the option jm no root in the localopts file to no.
AWSBDW033E
Jobman could not set the group access list for the user specified in the logon of the job. The operating system error is: "system_error".
Previous message text: Failed to set groups system_error.
system_error is the operating system error message.
Jobman proceeds.
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW034E
Jobman encountered an error processing the following command: "command" on the following file: "file_name".
Previous message text: Command (command) not allowed on file file_name with jm no root set.
The reason is one of the following:
- An opens file dependency includes special characters, such as pipe (|), or command in background (&).
- The option jm no root in the localopts file is set to yes.
file_name is the name of the file which jobman is working on. command is the command that cannot be used.
Jobman proceeds.
Do not use special characters in opens dependencies or change the option jm no root in the localopts options file to no.
AWSBDW036W
Jobman was unable to invoke the following method file: "method_file", because it was either not executable, unreadable or missing.
method_file is the name of the method file.
Jobman proceeds.
Check the correct name of the method file in <TWS_home>/methods and verify the access rights. When you have resolved the problem, rerun or reschedule the job.
AWSBDW037E
Jobman cannot get the status of an external dependency because the timeout jm look specified in the localopts file has been exceeded.
See message.
The method stops.
Verify that the remote system is reachable. If the access is slow, increase the value of the timeout jm look in the localopts file. When you have located the error, rerun or reschedule the job, as appropriate.
AWSBDW038E
Jobman cannot resolve an external dependency because it cannot check the status of the following external job: "external_job". This is because the workstation where the job is running is not an X-agent.
See message.
external_job identifies the external job.
Jobman proceeds.
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW039E
Jobman or jobmon could not resolve an external dependency on job "external_job". The operating system error is: "system_error".
external_job is the name of the external job (<workstation>#<external_job>). system_error is the operating system error message.
This is a message that is embedded in other error messages.
Jobman proceeds.
Check the response associated with the error specified by system_error. When you have located the error, rerun or reschedule the job, as appropriate.
AWSBDW040E
Jobman encountered a file descriptor problem while trying to resolve an external dependency. The operating system error is: "system_error".
Internal error: fdopen failed with errno = system_error.
system_error contains the operating system error message.
This is an operating system error generated by the I/O library function fdopen. It could occur if the process has opened too many file descriptors or if there is insufficient storage space available.
Jobman proceeds.
Verify that there is enough space available on the file system. If there is, increase the number of file descriptors a process can open, using the operating system facilities. Jobman will recheck the dependency after an interval (determined by the bm check files parameter in the localopts file. If the number of file descriptors increases or the number of file streams decreases, the external dependency check succeeds, otherwise the error condition will reoccur.
If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW041E
Jobman was unable to end the following user job: "job_name", #"job_number". This may happen when user kills jobs running on extended agents.
job_name is the name of the job that has not ended. job_number is the number that identifies this job in the process list (PID).
The program proceeds.
Stop the job manually.
AWSBDW053E
Jobman was unable to open the stdlist file for either the job process or itself. The operating system error is: "system_error"
system_error contains the operating system error message.
The program proceeds but if it was trying to open the stdlist for a job process, that process fails.
Check the file system of <TWS_home>/stdlist to ensure that there is sufficient space, and that the user has write permission. If a job failed, when you have resolved the problem, rerun or reschedule the job.
AWSBDW054E
Can not malloc environment array: !1
AWSBDW055E
Can not malloc buffer for environment variables: !1
AWSBDW057E
The job "job_name" was not launched for this reason: "error_message".
job_name is the name of the job.
error_message contains the reason for the failure. It is another HCL Workload Automation message.
Jobman proceeds.
Check the indicated message and implement the associated operator response.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW059E
Jobman cannot allocate sufficient memory to store its workstation table.
See message.
Jobman stops.
Check the following:
- Verify if the workstation has enough memory available. Information about the memory requirements of HCL Workload Automation is provided in the Release Notes. If not, you may need to increase the memory of the workstation or make changes in memory management and paging to make more memory available to jobman. Rerun jobman.
- If the workstation memory is adequate, try closing all the applications that you do not need, and then rerun jobman.
- If the problem persists, reboot the workstation, and then rerun jobman.
- If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW060W
Jobman was unable to add the following workstation: "workstation_name" to the workstation table, because the table is full. This is workstation record # "workstation_record_number".
Previous message text: CPU record #workstation_record_number for workstation_name, ignored, too many cpus.
workstation_record_number identifies the machine.
workstation_name is the name of the workstation.
The workstation table can hold up to 255 workstations.
The program proceeds, but the workstation record is ignored.
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW061E
Jobman encountered an error trying to read workstation information from the Symphony file.
See message.
Jobman stops.
This may be caused by a corruption of the Symphony file. To check if it is corrupt, view it with a file viewer and ensure that its contents look to be correct. If you suspect that it is corrupt, see the chapter in this guide on Symphony file corruption.
If the Symphony file does not seem to be corrupt, an internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW062E
Jobman was unable to invoke the following method file "method_file" for the extended agent. The operating system error is: "system_error".
system_error_number contains the operating system error message.
method_file is the name of the method.
The program stops.
Check that a method file with the indicated name exists in the <TWS_home>/methods directory and that the user running jobman has access rights to it. When you have resolved the access problem, resubmit the job that failed.
AWSBDW063E
Jobman was unable to find the following workstation: "workstation_name" in the workstation table.
This could occur because workstation_name is not in the Symphony file, or an error occurred while jobman was building the internal workstation table, or the Symphony file is corrupt.
workstation_name is the workstation jobman is searching for in the workstation table.
The program proceeds.
Verify that the indicated workstation name is a valid workstation.
- If it is correct, stop and restart the process to recreate the workstation table.
- If it is not correct, to check if the Symphony file is corrupt, view it with a file viewer and ensure that its contents look to be correct. If you suspect that it is corrupt, see the chapter in this guide on Symphony file corruption.
If the error persists it maybe that it is not possible to access this workstation for some unknown reason, in which case the job that jobman is processing will be ignored.
AWSBDW064E
A job that jobman is monitoring has returned the following unrecognizable message: "incorrect_message". The job identifier, monitor PID and method file are as follows: "job_name", #J"monitor_pid" using "method_file".
job_name identifies the extended agent job or the extended agent external job. monitor_pid is the PID of the method. method_file is the name of the method launched. incorrect_message is the message jobman cannot understand.
The program proceeds and the message is ignored.
Contact the owner of the extended agent method. Change the method to generate a recognizable message and re submit the job.
AWSBDW066E
The schedulr has asked jobman to run a task that is not supported on the targeted agent. The following method options file was used: "method_options_file". The job identifier and monitor PID are as follows: "job", #J"monitor_pid".
job identifies the extended agent job or the extended agent external job. monitor_pid is the PID of the method. method_options_file is the name of the method launched.
The program proceeds, but the operation is not performed.
Check which tasks are supported by the given extended agent. Modify the method and reschedule the job, if appropriate.
AWSBDW067E
The extended agent has returned an unrecognized state "invalid_state" for job "job", #J"monitor_pid".
- invalid_state is the state has been returned
- job identifies the extended agent job or the extended agent external job.
- monitor_pid is the PID of the method.
The program proceeds.
Check the HCL Workload Automation documentation for the valid states. Modify the method and reschedule the job, if appropriate.
AWSBDW068E
Jobman encountered a problem (getlogin failed) with the user name for a job. The operating system error is: "system_error"
Internal error: generated by a call to strerror (errno).
system_error is the system error message indicating why getlogin failed.
Jobman proceeds, but the job in question is not run.
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW069E
Jobman encountered a problem with the user name of the remote user that will launch a job on an extended agent. The operating system error is: "system_error"
Internal error: cuserid failed.
The system error message system_error is generated by a call to strerror (errno), and indicates why cuserid failed.
Jobman proceeds, but the job in question is not processed.
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW070E
Jobman cannot start. It has tried to become a daemon, giving the following internal error: "error" and system error: "system_error".
On UNIX only, when starting up, jobman tries to become a deamon. It disassociates itself from the terminal, closing all file descriptors.
error is the internal error type. system_error is the operating system error message.
The program cannot start.
Read carefully the system error and try to resolve it. search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW071E
The following script or command name: "script_name" has exceeded the maximum number of characters allowed: "maximum_number".
See message.
- script_name is the name of the script or command.
- maximum_number is the number of characters permitted.
The program proceeds, but the operation is not performed.
Change the indicated script or command name to a valid name with fewer characters than the indicated limit.
AWSBDW072E
Jobman encountered an error when removing the following centralized script file: "file_name". The operating system error is: "error_text".
In an end-to-end configuration the translator thread, running on OPCMASTER, has downloaded a centralized script to this workstation into the temporary file file_name. After the script has been run, jobman cannot remove the temporary file.
error_text is a string that describes the reason for the error. The information is retrieved from the operating system.
Jobman proceeds.
Resolve the problem indicated by the error message and manually delete the temporary file. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW073E
Jobman encountered an error when changing the owner of the following centralized script file: "file_name". The operating system error is: "error_text".
In an end-to-end configuration the translator thread, running on OPCMASTER, has downloaded a centralized script to this workstation into the temporary file file_name. Before the script is run, jobman needs to change the ownership of the script, but cannot.
error_text is a string that describes the reason for the error. The information is retrieved from the operating system.
Jobman proceeds, and runs the script without changing its ownership.
Resolve the problem indicated by the error message and reschedule or rerun the activity. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW074E
Jobman has exceeded the available memory while trying to allocate a buffer for the following centralized script file: "file_name".
In an end-to-end configuration the translator thread, running on OPCMASTER, has downloaded a centralized script to this workstation into the temporary file file_name. Jobman cannot allocate a buffer to load the file.
file_name is the file name of the local copy of the centralized script.
Jobman proceeds without running the script.
Check the following:
- Verify if the workstation has enough memory available. Information about the memory requirements of HCL Workload Automation is provided in the Release Notes. If not, you may need to increase the memory of the workstation or make changes in memory management and paging to make more memory available to jobman. Rerun jobman.
- If the workstation memory is adequate, try closing all the applications that you do not need, and then rerun jobman.
- If the problem persists, reboot the workstation, and then rerun jobman.
- If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW075E
Jobman (UNIX) or jobmon (Windows) encountered an error opening the following centralized script file: "file_name".
file_name is the file name of the local copy of the centralized script.
Jobman proceeds without running the script.
Verify that the HCL Workload Automation user has the rights to access the directory where the centralized scripts are written in the product directory structure, and the rights to open and read the scripts. Correct any problems you find and rerun or reschedule the job that used the script.
AWSBDW076E
The content of the following centralized script file is too long: "file_name".
The centralized script file cannot be more than 4096 characters in length.
file_name is the file name of the local copy of the centralized script.
Jobman proceeds without running the script.
Limit the size of the centralized script stored within the JOBLIB to no more than 4096 characters. Rerun or reschedule the job.
AWSBDW077E
The following centralized script file is empty: "file_name".
In an end-to-end configuration the translator thread, running on OPCMASTER, has downloaded a centralized script to this workstation into the temporary file file_name The file is empty.
The most probable cause is that a problem occurred during the download of the file to the workstation. It may also be possible that the file was empty before the download.
file_name is the file name of the local copy of the centralized script.
Jobman proceeds without running the script.
Attempt to repeat the process so that the script is downloaded again. If the problem persists, check if the script was empty before the download.
AWSBDW078W
The promotion value specified in the localopts file is greater than zero. Values that are greater than zero are not valid and are set to -1.
Positive promotion values do not work correctly and decrease system performance.
Jobmon automatically set the promotion value to -1.
Check the values defined in the localopts file and assign the correct promotion values.
AWSBDW079E
Jobman could not run the job because the system call used to launch the job failed: Jobmon was unable to retrieve user information.
See message.
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDW210W
The Realtime priority value specified in the localopts file is not supported. High priority will be used.
See message.
Jobmon proceeds using the High priority setting..
Check the values defined in the localopts file and assign the correct priority values.
AWSBDW301E
Jobman was unable to successfully access a mailbox record in its Mailbox.msg file, Courier.msg, giving the following error type and number: "error_type" - "error_number". The problem was identified in the following source file: "source_file" and the function being performed is: "function_name".
source_file is the name of the source file where the error occurred. function_name is the name of the function where the error occurred (read_courier or delete_courier). error_type is the internal error type for event file messages (unison.msg - set 106). error_number is the internal error number.
If the error number is zero, it means that jobman cannot delete the Mailbox.msg file.
If the error number is greater than zero, it probably indicates that batchman has failed, and is thus not writing to the Mailbox.msg file.
Jobman stops.
Check the batchman log message for the explanation. If you can see why batchman failed, and can recover from the situation, you should do so, and then restart batchman and jobman (in that order).
If you cannot resolve the batchman failure, or the problem persists, an internal error has occurred. search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.