AWSBHT - Batchman messages
This section lists error and warning messages that might be issued by the batchman component.
The message component code is BHT.
AWSBHT001E The job "job_name" in file "file_name" has failed with the error: "error_message"
Explanation
Batchman encountered an error launching a job. The job has been put in the state FAIL. This can happen for many reasons:
- Jobman is not able to open the stdlist file where it redirects the job standard output and error, because either it cannot find the directory or it cannot create it.
- If the job is run from a file, the user might not have access to the file.
- The job must run on a hosted extended agent and the user who must launch the job does not have permission to access the extended agent method.
- Jobman is not able to read the entry of the job in the internal jobtable.
- Jobman is not able to update the record in the internal jobtable.
- Jobman cannot retrieve the user's password.
- The user is not authorized to run the job as root.
- Jobman failed to set the GID for the secondary user group.
- Jobman failed to set the GID for the primary user group.
- Jobman failed to set the UID.
- Jobman cannot change to the home directory of the user.
- Jobman failed to set the SID.
- Jobman is not able to launch the MONITOR for the job.
- Jobman is not able to fork the job process.
job_name is the name of the job (<workstation>#<job_stream >.<job>) that batchman is launching. file_name is the name of the JCL file. error_message describes the error and includes the operating system error message.
System action
Batchman proceeds. The job has not been launched.
Operator response
Use the error_message to solve the problem.
The most common causes are the following:
- The password you specified for the user (within the userdata mozart database) is wrong, not valid, expired or the account is locked (only for Windows jobs). In this case change the user password using composer
- The JCL file name you specified for the job is incorrect or the file cannot be found (both UNIX and Windows). Verify the JCL name you specified in the job definition exists in the correct directory.
- Access rights to the JCL file or the HCL Workload Automation binaries are not correct. Verify that the JCL has the right access rights.
AWSBHT002W Job logs on differently than documentation indicates.
AWSBHT003E Batchman is unable to allocate memory for its internal record table during initialization.
Explanation
See message.
System action
Batchman stops.
Operator response
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 batchman. Rerun batchman.
- If the workstation memory is adequate, try closing all the applications that you do not need, and then rerun batchman.
- If the problem persists, reboot the workstation, and then rerun batchman.
- If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHT004E Batchman has read a record in the message file which has the following destination workstation ("to_workstation") that cannot be found. The message originated at the following workstation: "from_workstation".
Explanation
Batchman has read from its message file, Intercom.msg, a record with a destination workstation did not match that of batchman or any of the extended agents hosted by it.
to_workstation is the name of the destination workstation. from_workstation is the name of the origin workstation.
System action
Batchman continues, but the record in the message file is ignored.
Operator response
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.
AWSBHT005E Batchman has read a record in the message file which identifies a job which cannot be found in the Symphony file.
Explanation
Batchman read a record from its local message file, Intercom.msg. The record is a job ID whose record batchman could not find in the Symphony file.
System action
Batchman continues, but the record in the message file is ignored.
Operator response
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.
AWSBHT006E Batchman has read a Job Terminate record in the message file for a job that is not in the execute state.
Explanation
Batchman read from its mailbox file, Intercom.msg, a Job Terminate record for a job that is not in the execute state.
System action
Batchman continues, but the record in the message file is ignored.
Operator response
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.
AWSBHT007W Record type mismatch reading SYMPHONY file
AWSBHT008E Batchman has read a record in the message file which has either an incorrect length, or the following unrecognized record type: "record_type".
Explanation
Batchman read a record from its local message file, Intercom.msg with an unknown type or a length which does not match the correct record type length. record_type is the type of the record, a two character string.
System action
Batchman continues, but the record in the message file is ignored.
Operator response
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.
AWSBHT009E Batchman has found a non-valid dependency type in the Symphony file.
Explanation
Batchman found an invalid dependency type in the Symphony file. This message is issued also when a mailbox add dependency record with an unknown dependency type is processed by batchman.
System action
Batchman continues, but the record in the message file is ignored.
Operator response
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.
AWSBHT010E Batchman has received a mailbox message that updates the state of a job, but the job cannot be found in the Symphony file.
Explanation
See message.
System action
Batchman continues, but the record in the message file is ignored.
Operator response
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.
AWSBHT011E Batchman found corrupted job recovery information while it was attempting to determine the recovery action for a job that terminated with an ABEND state.
Explanation
See message.
System action
Batchman continues, but the recovery action for the job is not performed.
Operator response
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.
AWSBHT012E The batchman internal job table or its extension area is full.
Explanation
The batchman internal Symphony file record table or its extension area is full.
Batchman has run out of entries in the jobtable or its extension area in system memory. The extension area is used to record ad hoc work, restart jobs, and manage the iterations of the jobs that use the every keyword.
System action
Batchman stops.
Operator response
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 batchman. Rerun batchman.
- If the workstation memory is adequate, try closing all the applications that you do not need, and then rerun batchman.
- If the problem persists, reboot the workstation, and then rerun batchman.
- If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHT013E Batchman has received a mailbox message that refers to the following job stream: "job_stream_name". However, the job stream does not exist in the Symphony file.
Explanation
See message.
job_stream_name is the name of the job stream.
System action
Batchman continues, but the record in the message file is ignored.
Operator response
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.
AWSBHT014E Batchman has received a mailbox message that refers to the following job: "job_name". However, the job does not exist in the Symphony file.
Explanation
See message.
job_name is the name of the job.
System action
Batchman continues, but the record in the message file is ignored.
Operator response
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.
AWSBHT015W Batchman cannot release a job stream from its dependencies because the job stream is not in the holding state that is required to allow it to be updated.
Explanation
This message explains why an event has been discarded.
The situation can occur when a job stream changes its state before the event that required a release of the dependencies (generated by conman or the Job Scheduling Console) arrived at the workstation where batchman is running.
System action
Batchman continues, but the event is ignored.
Operator response
No action is required.
AWSBHT016W Batchman cannot release a job from its dependencies because the job is not in the holding state that is required to allow it to be updated.
Explanation
This message explains why an event has been discarded.
The situation can occur when a job changes its state before the event that required a release of the dependencies (generated by conman or the Job Scheduling Console) arrived at the workstation where batchman is running.
System action
Batchman continues, but the event is ignored.
Operator response
No action is required.
AWSBHT017E Batchman has received a mailbox message that refers to a job stream that cannot be found in the Symphony file.
Explanation
Batchman read from Intercom.msg a mailbox record that modified the dependencies or the state of a job stream. However, batchman was not able to find the job stream record in the Symphony file.
System action
Batchman continues, but the record in the message file is ignored.
Operator response
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.
AWSBHT018E Batchman has received an event that refers to the following job that cannot be found in the Symphony file: "job_name".
Explanation
See message.
job_name is the name of the job batchman cannot find.
System action
Batchman continues, but the event is ignored.
Operator response
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.
AWSBHT019E Batchman was unable to modify a job because it is not in the valid state to apply the modification.
Explanation
This message explains why an event has been discarded.
Some job actions can only be applied if the job is in the appropriate state. For example, a job cannot be stopped if it is in the SUCC state (it has already stopped).
The situation can occur when a job stream changes its state before the event (generated by conman or the Dynamic Workload Console) arrived at the workstation where batchman is running.
System action
Batchman continues, but the event is ignored.
Operator response
No action is required.
AWSBHT020E Batchman has received an event for a prompt that cannot be found in the Symphony file.
Explanation
See message.
System action
Batchman continues, but the event is ignored.
Operator response
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.
AWSBHT021E Batchman has received an event to add a new job stream to the plan, but a job stream with that name already exists in the Symphony file.
Explanation
See message.
System action
Batchman continues, but the event is ignored.
Operator response
Check if two job streams with the same name have been submitted in quick succession (either the same job stream twice, or 2 different job streams but with the same name). Normally, you are not able to submit two job streams with the same name, but it is possible that a synchronization error has occurred if they were submitted in quick succession.
If you have submitted the same job stream twice, you need take no action - the second occurrence is ignored.
If you have submitted two different job streams with the same name, resubmit the second job stream using an alias name.
AWSBHT022E Batchman has received an event for a job stream or a job within a job stream, but the job stream cannot be found in the Symphony file.
Explanation
See message.
System action
Batchman continues, but the event is ignored.
Operator response
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.
AWSBHT023E While responding to a submit schedule request, batchman has found a record in the message file which is not a job stream, job or dependency record.
Explanation
Batchman is processing a conman submit sched request, for which it expects to find a set of job stream, job, and dependency records in the message file. However, while processing this set it has found a record type that is not one of these. The message file is corrupt, or an internal error has occurred.
System action
Batchman proceeds. The job stream that was submitted might not be added to the Symphony file. If it is added, a job or dependency might be missing.
Operator response
Run the stop <workstation> and then the start <workstation>commands to regenerate the mailbox file.
If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHT024W Batchman has received an end-event for a job stream, but the job stream is not in the correct status to receive an end-event.
Explanation
This message explains why an event has been discarded.
Some actions can only be applied if the job stream is in the appropriate state. In this case, an end-event cannot be processed if the job stream state is not ADDING.
The situation can occur when a job stream changes its state before the event (generated by conman or the Dynamic Workload Console) arrived at the workstation where batchman is running.
System action
Batchman continues, but the event is ignored.
Operator response
No action is required.
AWSBHT025W Batchman has received an end-event for a job, but the job is not in the correct status to receive an end-event.
Explanation
This message explains why an event has been discarded.
Some actions can only be applied if the job is in the appropriate state. In this case, an end-event cannot be processed if the job state is not ADDING.
The situation can occur when a job changes its state before the event (generated by conman or the Dynamic Workload Console) arrived at the workstation where batchman is running.
System action
Batchman continues, but the event is ignored.
Operator response
No action is required.
AWSBHT026E Batchman has received an event for the following resource, but the resource cannot be found in the Symphony file: "resource_name".
Explanation
See message.
resource_name is the name of a physical or logical scheduling resource that cannot be found in the Symphony file.
System action
Batchman proceeds.
Operator response
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.
AWSBHT027W Batchman has received an event to add a new job to a job stream, but a job with that name already exists in the job stream in the Symphony file.
Explanation
See message text. Two or more jobs with the same name can only be present in the USERJOBS job stream.
System action
Batchman continues, but the event is ignored.
Operator response
Check if two jobs with the same name have been submitted in quick succession (either the same jobs twice, or 2 different jobs but with the same name). Normally, you are not able to submit two jobs with the same name, but it is possible that a synchronization error has occurred if they were submitted in quick succession.
If you have submitted the same job twice, you need take no action - the second occurrence is ignored.
If you have submitted two different jobs with the same name, resubmit the second job using an alias name.
AWSBHT028E Batchman has received an event for a FILE dependency, but the dependency cannot be found in the Symphony file:
Explanation
See message.
System action
Batchman continues, but the event is ignored.
Operator response
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.
AWSBHT029E Batchman was unable to allocate memory to hold the internal workstation table that contains the workstations for which batchman schedules jobs. The number of entries it wants to create is as follows: "table_entries".
Explanation
table_entries is the number of workstation entries for which batchman is trying to allocating memory.
System action
Batchman stops.
Operator response
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 batchman. Rerun batchman.
- If the workstation memory is adequate, try closing all the applications that you do not need, and then rerun batchman.
- If the problem persists, reboot the workstation, and then rerun batchman.
- If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHT038W The internal workstation table used by batchman is full. Workstation record #"workstation_record_number" for "workstation_name", has been ignored.
Explanation
The internal workstation table used by batchman is limited to 255 entries. This should be sufficient for any normal working situation. The fact that the table is full indicates that an internal error has occurred.
workstation_record_number identifies the machine. workstation_name is the name of the workstation.
System action
Batchman continues, but the workstation record is ignored.
Operator response
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.
AWSBHT044E Batchman could not find the entry for the following resource: "resource_name" in the dependency list for the following job stream or job: "job_stream_or_job".
Explanation
A conman release sched command has been issued to release the dependencies on the indicated job stream or job. However, the command refers to a resource that batchman cannot find as a dependency for job stream or job.
resource_name is the resource name that cannot be found.
job_stream_or_job is the name of the job stream or job that depends on the resource.
System action
Batchman proceeds.
Operator response
You need to contact the person who issued the conman release sched command, and determine the circumstances in which it was issued. These could be any of the following:
- When the command was issued, the resource name was typed incorrectly. Reissue the command, typing the resource name correctly.
- When the command was issued, the resource name was typed correctly, but the command identified the wrong job stream or job. Reissue the command, typing the job stream or job name correctly.
- The command was issued in error, attempting to release a resource from a job stream or job that had never depended on that resource. Take no action.
- Two operators separately issued the command to release the dependencies at about the same time. The first command to arrive at the workstation has been correctly processed. The second command would give this error. Take no action.
AWSBHT049E Batchman could not find a job or job stream as a holder in the list of holders in the Symphony file resource record with the following record number: "record_number".
Explanation
A holder is defined as a job stream or job that has need of a resource. In the Symphony file record for the resources in the plan there is a resource record which lists the holders of that resource. This internal error occurs if a job stream or job refers to a resource, but the job stream or job is not listed as a holder in the corresponding resource record.
record_number is the Symphony file record number for the job stream or job that is the holder of the resource.
System action
Batchman proceeds.
Operator response
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.
AWSBHT050E An internal error has occurred. Batchman has received an event from a master domain manager, from which this event should not have been produced.
Explanation
See message.
System action
Batchman proceeds. The event is ignored.
Operator response
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.
AWSBHT051W The number of dependencies specified in the following resolve dependency record "resolve_dependency_record" exceeds the total dependencies defined in the Symphony file: "dependencies_in_symphony". The job is the following: "job_or_job_stream_name".
Explanation
This probably indicates a synchronization problem. For example, it may be that a dependency has been added to a job and then deleted. If the dependency deletion reaches the workstation before the add, this error could occur.
resolve_dependency_record is the number of the record that contains the dependency that cannot be processed.
dependencies_in_symphony is the total number of dependencies contained in the Symphony file.
job_or_job_stream_name identifies the job or job stream for which the dependency cannot be processed.
System action
Batchman proceeds. The dependency record is not processed. The job that depends on this dependency record may wait indefinitely for the resolution of this dependency, unless some remedial action is taken.
Operator response
Check the status of the job in question. If it is waiting for a dependency, you can release or delete the dependency, using conman.
If the job is being processed it probably indicates that Batchman encountered a synchronization problem but then resolved it.
AWSBHT052W Requested dependency type !1 is not equal to actual type of !2.
AWSBHT056E Batchman was unable to add a dependency to a job stream or job, because the number of dependencies in the record is already equal to the maximum allowed (40).
Explanation
See message.
System action
Batchman, but the event is ignored.
Operator response
Wait until the next plan generation (JnextPlan) to add a dependency. Even if you delete one or more dependencies from the job stream or job, you can probably not add a new dependency until after the next JnextPlan.
AWSBHT057W Batchman has found a non-valid run number in the Symphony file for the following record type: "record_type" and object: "object".
Explanation
See message.
record_type is the record type of the record in the Symphony file with the non valid run number.
object is the object of the record with the non valid run number, for example, job stream, job, or resource.
System action
Batchman proceeds. The record is ignored.
Operator response
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.
AWSBHT060W CS record ignored !1
AWSBHT061E Batchman has received a mailbox record indicating that the following job has stopped unexpectedly: "job_name" ("job_number").
Explanation
job_name is the name of the job (<workstation>#<job_stream>.<job>).
job_number is the number assigned to the job.
System action
Batchman continues. The indicated job has stopped.
Operator response
Use internal policies to determine how to handle the stopped job. All jobs depending on the stopped job wait until the job is rerun successfully or until it is cancelled. Stopped jobs that have the continue recovery option do not prevent dependent jobs from running.
AWSBHT069E The following job stream is in the stuck state: "job_stream_name".
Explanation
A job steam might become stuck for any of the following reasons:
- Jobs in the job stream cannot launch because they depend on a job that has failed. This is the most common reason.
- Operator intervention is required for a reply to a prompt on one of the jobs in the job stream.
- A job on which another depends cannot launch because its priority is zero.
job_stream_name is the name of the job stream that is stuck.
System action
Batchman continues. The indicated job has stopped.
Operator response
For a failed job, use your internal policies to determine how to handle it. You can either cancel the job to satisfy the other job dependencies or rerun it again successfully.
For a prompt, reply to the active prompt to change the status and free a stuck job.
For a zero priority, altering the value to any number greater than 0 changes the status and frees a stuck job.
AWSBHT087E Batchman has determined that jobman has failed with the following exit code: "exit_code".
Explanation
exit_code is jobman's exit status code.
System action
Batchman continues.
Operator response
See the section about jobman in the FAQ, on the HCL Workload Automation support web page, to see if the error matches any of the errors described in the section. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
AWSBHT089E A resource cannot be allocated to a job or a job stream because the maximum number of resource holders (32) has been reached.
Explanation
For each resource defined in a job stream or job, batchman creates a holder for that resource and that job stream or job. Batchman can manage a maximum of 32 active holders for each resource. This means that no more than 32 job streams or jobs can use the same resource at the same time.
System action
Batchman continues. The resource is ignored.
Operator response
Check in the log to determine the job or job stream that wanted to use the resource. This job or job stream might need to be rerun when some of the instances of the required resource have been freed.
If the condition that has given rise to the error is one that might re-occur, modify the job streams or jobs and the resource definitions. Split the resource into two or more resources maintaining the same number of resource instances between all of them. Distribute these resources between the job streams or jobs.
For example, suppose you have a resource called tape that has a value of 100. If you have 40 jobs that need to run at the same time and all need this resource, create a second resource called, for example, more_tape and allocate 50 to it, reducing the value of tape also to 50 (to maintain the same total value). Allocate these two resources equally to the 40 jobs or job streams so that if all of the jobs were running at the same time the total number of holders of either tape or more_tape would be 20, and would never exceed 32.
AWSBHT090E Batchman could not start jobman. The following gives more details of the error: "error_text".
Explanation
See message.
error_text describes at what step of the jobman creation process the error occurred, and the operating system error.
System action
Batchman continues.
Operator response
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.
AWSBHT091E Batchman could not open the Symphony file. The following gives more details of the error: "error_text".
Explanation
See message.
error_text contains the text of the error indicating why batchman could not open the Symphony file.
System action
Batchman stops.
Operator response
Make sure that a Symphony file exists with the correct file permissions and ownership in the HCL Workload Automation directory. If one does not exist, take the following steps to recreate it:
- Copy the Symphony file from the backup master.
- Start and link to the agent from the master.
If the error occurs at the beginning of the production day, do the following:
- Use the conman shut command to stop netman on the agent.
- Issue the StartUp command.
- From the master, issue the start command for the agent.
AWSBHT092E Batchman could not open the mailbox file Intercom.msg. The following gives more details of the error: "error_text".
Explanation
See message. Batchman reads and processes mailbox records from this file.
error_text contains the reason why batchman could not open the file.
System action
Batchman stops.
Operator response
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.
AWSBHT093E Batchman could not open the mailbox file Mailbox.msg. The following gives more details of the error: "error_text".
Explanation
See message. Batchman writes mailbox records to this file and mailman processes them.
error_text contains the reason why batchman could not open the file.
System action
Batchman stops.
Operator response
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.
AWSBHT094E Batchman could not open the mailbox file Courier.msg. The following gives more details of the error: "error_text"
Explanation
See message. Batchman writes mailbox records to this file and jobman processes them.
error_text contains the reason why batchman could not open the file.
System action
Batchman stops.
Operator response
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.
AWSBHT095E Batchman could not access the mailbox file Symphony.msg for reading or writing. The following gives more details of the error: "error_text"
Explanation
See message.
error_text contains the reason why batchman could not access the Symphony file.
System action
Batchman stops.
Operator response
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.
AWSBHT096E Batchman could not read from the mailbox file Intercom.msg. The following gives more details of the error: "error_text"
Explanation
See message. Batchman writes mailbox records to this file and mailman processes them.
error_text contains the reason why batchman could not read the file.
System action
Batchman stops.
Operator response
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.
AWSBHT097E Batchman could not write to the mailbox file Intercom.msg. The following gives more details of the error: "error_text"
Explanation
See message. Batchman writes mailbox records to this file and mailman processes them.
error_text contains the reason why batchman could not open the file.
System action
Batchman stops.
Operator response
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.
AWSBHT098E Batchman could not write to the mailbox file Courier.msg. The following gives more details of the error: "error_text"
Explanation
See message. Batchman writes maibox records to this file and jobman processes them.
error_text contains the reason why batchman could not open the file.
System action
Batchman stops.
Operator response
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.
AWSBHT099E AAn internal error has occurred. Batchman could not write to the mailbox file Server.msg. The following error was generated: "error_text"
Explanation
Batchman writes maibox records to the Server.msg file and PlanMonitor processes them.
error_text contains the reason why batchman could not open the file.
System action
Batchman stops.
Operator response
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHT156E Batchman could not open the mailbox file DeadMessage.msg. The following gives more details of the error: "error_message"
Explanation
See message.
error_message describes the error and includes the operating system error message.
System action
Batchman stops.
Operator response
Verify that there is sufficient space in the file system of the ftbox directory and that the TWSuser has the authority to create files in that directory. If not, create more space or grant the user that authority.
If one of these is not the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHT157E Batchman could not read the mailbox file DeadMessage.msg.
Explanation
See message text.
System action
Batchman proceeds.
Operator response
Verify if the TWSuser has the authority to read files in ftbox directory. If not, grant the user that authority.
If this is not the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHT158E Batchman could not write to the mailbox file DeadMessage.msg. The message has been lost.
Explanation
See message.
System action
Batchman proceeds, but the message that it wanted to write to the deal message queue could not be written, and has been lost.
Operator response
To avoid problems with other messages destined for this queue, verify that there is sufficient space in the file system of the ftbox directory and that the TWSuser has the authority to create files in that directory. If not, create more space or grant the user that authority.
If one of these is not the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHT159E Batchman could not write to the mailbox file DeadMessage.msg because the file is full. The message has been lost.
Explanation
See message. Incoming messages refer to missing objects in Symphony file and they are discarded if the file is full.
System action
Batchman proceeds.
Operator response
Verify if any secondary link from another workstation to this workstation is not working, and if so, perform a link command to restore it. Remember that if a workstation does not open the primary link and all its secondary links it is not fully linked.
AWSBHT160E The EvtLog message file is full, events will not be logged until a new Symphony is produced. Recovery with event reapply is no more possible until that time.
AWSBHT210E Batchman encountered an error because the user name is not defined in the Symphony file.
Explanation
See message.
System action
Batchman proceeds.
Operator response
This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHT212W Batchman has determined a negative value for the run time for a job. The following error text contains useful information about the job: "error_text"
Explanation
See message.
error_text contains time related information about the job. Possible message are the following:
- Elapsed time: [time]
- Start date: [date]
- Start time: [time]
- End date: [date]
- End time: [time]
- Record Num: [number]
- Calculated negative elapse time for job job_name
System action
Batchman proceeds. The job is not run.
Operator response
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHT214E Batchman could not create a new Sinfonia file during the network synchronization processing.
Explanation
See message.
System action
Batchman stops.
Operator response
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.
AWSBHT215E Batchman could not open a new Sinfonia file during the network synchronization processing.
Explanation
Batchman was unable to open the Sinfonia file during the network synchronization processing.
System action
Batchman stops.
Operator response
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.
AWSBHT216E Batchman could not access the Sinfonia file during the network synchronization processing.
Explanation
See message.
System action
Batchman stops.
Operator response
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.
AWSBHT217E Batchman encountered an error while trying to allocate memory for its internal CPU table (calloc or realloc).
Explanation
See message.
System action
Batchman stops.
Operator response
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 batchman. Rerun batchman.
- If the workstation memory is adequate, try closing all the applications that you do not need, and then rerun batchman.
- If the problem persists, reboot the workstation, and then rerun batchman.
- If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHT228W The latest time that job stream "job_stream_name" can start has already passed.
Explanation
See message (corresponds to the Until time in legacy Maestro).
job_stream_name is the name of the job stream that is late.
System action
Batchman proceeds.
Operator response
Use the conman submit command if you want to run the indicated job stream.
AWSBHT230W Warning: Dependency !1 not found in Symphony;ignored.
AWSBHT231W A duplicated job termination (JT) record has been received for the following job: "job_name".
Explanation
Duplicate job termination messages have been received in respect of the same job.
The probable reason is that the job finished at about the same time as JnextPlan was run, and a brief synchronization problem occurred.
System action
Batchman continues.
Operator response
Compare the status of the job received on this workstation with the status of the job recorded at other workstations.
If you find different job statuses recorded in different places, and other jobs have FOLLOWS dependencies with respect to this job, you should resolve those dependencies manually.
If there are no dependencies, the presence of duplicate job termination records needs no action on your part.
AWSBHT233W An incorrect dependency has been detected for the following jobstream: "sched".Priority will be set to 0.
Explanation
The dependency record gets somehow corrupted. Batchman was unable to determine if the dependency was satisfied or not.
System action
Batchman cleaned out the dependency and set the priority to 0 to prevent job or jobstream from run.
Operator response
Check if the jobstream can run. If yes, change its priority.
AWSBHT234W An incorrect dependency has been detected for the following job: "job".Priority will be set to 0.
Explanation
The dependency record gets somehow corrupted. Batchman was unable to determine if the dependency was satisfied or not.
System action
Batchman cleaned out the dependency and set the priority to 0 to prevent job or jobstream from run.
Operator response
Check if the job can run. If yes, change its priority.
AWSBHT235E An internal error has occurred. Batchman could not write to the mailbox file planbox.msg. The following error was generated: "error_text"
Explanation
Batchman writes maibox records to the Planbox.msg file and PlanboxMonitor processes them.
error_text contains the reason why batchman could not open the file.
System action
Batchman continues.
Operator response
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHT236E An internal error has occurred. Batchman could not write to the mailbox file mirrorbox.msg. The following error was generated: "error_text"
Explanation
Batchman writes maibox records to the mirrorbox.msg file and PlanUpdateMonitor processes them.
error_text contains the reason why batchman could not open the file.
System action
Batchman continues.
Operator response
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBHT237E An internal error has occurred. Batchman is unable to extend the Symphony file and then it cannot manage the mailbox message queue. A possible cause is a full file system.
Explanation
Batchman is unable to update the symphony file.
System action
Batchman exits.
Operator response
Check the file system and restart the agent.