HCL Workload Automation, Version 9.4

AWSBCV - Mailman messages

This section lists error and warning messages that might be issued by the mailman component.

The message component code is BCV.

AWSBCV001E   Batchman has failed with an internal error, producing the following status code: "status".

Explanation

Mailman issues this message when batchman terminates unexpectedly. status contains an operating system exit status message relating to batchman.

System action

Batchman stops. Mailman continues.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV002E   Error building !1, Error !2

AWSBCV003E   Mailman was unable to start one of the internal components ("program") of batchman. The system error message is "system_error"

Explanation

Mailman was unable to start the batchman process.

program is the fully qualified name for the batchman internal component that could not start. system_error is the operating system error message.

System action

Batchman did not start. Mailman continues.

Operator response

Use the program and attempt to locate the executable. Make sure that it has the correct file access permission. If you locate the program successfully and it has the correct permissions, stop all HCL Workload Automation processes and restart them. If you cannot find the program, or you find it and restart HCL Workload Automation but the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV004E   Mailman was unable to start one of its internal components ("program") due to an internal error. The operating system error message is "system_error".

Explanation

Mailman was unable to start a mailman server process.

program is the fully qualified name for the batchman internal component that could not start. system_error is the operating system error message.

System action

Mailman did not start.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV005E   Mailman encountered an internal error opening the following file: "file_name". The operating system error message is "error_message".

Explanation

Mailman was unable to open either the Courier.msg or the Intercom.msg files for writing. Courier.msg is opened when mailman is running on a standard agent or broker workstation.

file_name is the fully qualified name for the message file. error_message is a message that describes the error and includes the operating system error message.

System action

Mailman did not start.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV006E   Workstation "workstation_name" cannot be added to the mailman table because there are more workstations than the maximum allowed.

Explanation

workstation_name is the name of the workstation that mailman has failed to add to its table.

System action

The operation is not performed. This message is produced for all workstations that mailman is trying to add to the table in excess of the maximum allowed. Mailman proceeds, ignoring this workstation.

Operator response

Try to limit the number of workstations (should not be greater than 100000). If you succeed, retry the operation.

AWSBCV007E   The workstation "workstation_name" cannot be accessed.

Explanation

There are two possibilities:

  1. The program cannot find the workstation_name in its table. An internal error has occurred.
  2. The program finds the workstation in its table, but the workstation is not in the current domain and thus the program cannot link to it.

System action

If the program can link to the workstation's domain manager, it will pass all messages for the workstation to that domain manager. Otherwise, such messages are discarded. the program proceeds.

Operator response

Verify that the workstation_name correctly describes a workstation. If it is correct, verify that the workstation cannot be linked to. If it cannot be linked to you should investigate why, and correct the problem. If it can be linked to, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV008E   A message file cannot be opened; the operating system gives the following error: "error_message"

Explanation

This can be one of two possibilities:

  1. Mailman is unable to open its message file: Mailbox.msg
  2. A mailman server process is unable to open its message file pobox/[server].msg.

error_message is a message that contains information about the error and includes the operating system error message.

A possible reason is that either your HCL Workload Automation user or your system has too many files open (a typical user is limited to 64 files).

System action

Mailman stops.

Operator response

Attempt to resolve the operating system error. Use the limit command to see the user's file limits (the file limit is the 'descriptor' line for csh users).

If the problem is with the number of files open, take one of the following actions, according to whether the problem is with the operating system limits or a user's limits:

  • Add the following lines to your system parameters file (/etc/system) and reboot the system:

    set rlim_fd_max = 4096

    set rlim_fd_cur = 1024

    This may consume slightly more available memory, but it speeds up the system.
  • Modify your HCL Workload Automation user environment (the following is correct for a csh user):

    limit descriptors nnn

    where nnn is a value greater than the value revealed by the limit command.

Restart mailman.

AWSBCV009E   Mailman could not open the workstation message file: "file_name" in the PO box. The following gives more details of the error: "error_message".

Explanation

Mailman is not able to open a workstation message file in the HCL Workload Automation pobox directory.

file_name specifies the name of the message file.

error_message describes the error and includes the operating system error message.

System action

Mailman may stop. If it continues, it will not perform any message processing for this workstation.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV010E   Error opening Symphony on !1

AWSBCV011E   Error reading cpu records, Error !1

AWSBCV012E   Mailman cannot read a message in a message file. The following gives more details of the error: "error_message".

Explanation

Mailman was unable to read a message from its local mailbox: Mailbox.msg, or [Server].msg for a server mailman.

error_message describes the error and includes the operating system error message.

System action

Mailman continues.

Operator response

Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV013E   Error server jcw bad for !1

AWSBCV014E   Mailman could not start the following mailman server: "server_name". The following gives more details of the error: "error_message".

Explanation

Mailman encountered an error trying to start the desired mailman server.

server_name is the name of the mailman server which mailman is trying to start. error_message is a message which explains why the server could not be started.

System action

Mailman proceeds.

Operator response

Taking into consideration what is written in the error_message, check if the network and the operating system are working correctly. If this check does not reveal any reason why the server could not be started, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV015E   Mailman was unable to write a message to the PO box message file for workstation: "workstation_name". The following gives more details of the error: "error_message".

Explanation

workstation_name is the name of the workstation for which the message file could not be written.

error_message describes the error and includes the operating system error message.

System action

Mailman proceeds.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV024W   Mailman has lost communication with the following workstation: "workstation_name".

Explanation

The writer of the workstation, identified by workstation_name, is either busy, or is not responding due to communication problems.

System action

No further messages are processed for this workstation. Mailman proceeds.

Operator response

Use the ping command to verify that the workstation is accessible in the network. If you are able to access the workstation, unlink and re-link the workstation, using the conman commands unlink <workstation_name> and link <workstation_name>.

If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV025W   Mailman has unlinked from workstation: "workstation_name".

Explanation

Mailman has not received a communication from the workstation identified by workstation_name for a period longer than its configured time-out period, so it unlinks from the workstation.

System action

No further messages are processed for this workstation. Mailman proceeds.

Operator response

Verify that the workstation is available and working, using the ping command. If it is, take no action; if it is not, take whatever network action or action at the workstation that is necessary to allow the connection to be remade. If you want to remake the connection manually, use the conman command link <workstation_name>.

AWSBCV034W   Impossible branch taken: file: !1, line: !2

AWSBCV035W   Mailman was unable to link to workstation: "workstation_name"; the messages are written to the PO box.

Explanation

Mailman was unable to link to the workstation workstation_name, for an unknown reason.

System action

All messages for this workstation are written to the message file in the PO box directory (pobox). Mailman attempts, at a configurable interval, to re-establish the link to the workstation. As soon it succeeds, the messages in the PO box are sent to the workstation. Mailman proceeds.

Operator response

If you are not expecting the workstation to be unavailable, do the following:

  1. Use the ping command to check the workstation's availability. If it is now available, you can link to it manually, or leave mailman to relink to it automatically.
  2. Verify that netman on the workstation is working, running StartUp on the workstation if it is not.
  3. Verify that netman on the workstation is listening on the specified netman port, by checking that the netman port specified in the database definition is the same as the port specified in the localopts file on the workstation.

If you want to change the frequency with which mailman attempts to relink to the workstation, modify the appropriate parameter in the localopts file.

If you want to attempt to relink manually to the workstation launch the conman command link <workstation_name>.

AWSBCV036W   Mailman cannot link to the following workstation: "workstation_name" because it has an incompatible Symphony file.

Explanation

Mailman encountered a problem while trying to link to its parent workstation: workstation_name because the workstation has an incompatible Symphony file and needs to be initialized first. Probably the run number of the Symphony file on the workstation is less than the run number of the child Symphony file.

A new Symphony file cannot be sent, because the workstation mailman is trying to link to is not its domain manager.

System action

Mailman proceeds.

Operator response

Verify that workstation_name can connect to this workstation and if it can, remove its Symphony file.

The chapter in this guide on 'Symphony file corruption'.

AWSBCV037E   Mailman encountered an internal error while it was reading the Sinfonia file. The following gives more details of the error: "error_message ".

Explanation

Mailman sends the Sinfonia file to each workstation when it links to the workstation.

error_message contains the fully qualified name of the Sinfonia file and includes the operating system error message.

System action

Mailman stops.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV038E   Mailman encountered a memory problem while downloading the Symphony file to workstation. Mailman failed to allocate the memory necessary to store the information that it needs to read from the Sinfonia file: "workstation_name"

Explanation

Mailman failed to allocate the memory necessary to store the information that it needs to read from the Sinfonia file.

System action

Mailman proceeds.

Operator response

Check the following:

  1. 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 mailman. Rerun mailman.
  2. If the workstation memory is adequate, try closing all the applications that you do not need, and then rerun mailman.
  3. If the problem persists, reboot the workstation, and then rerun mailman.
  4. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
The Release Notes for details of memory requirements.

AWSBCV040W   Mailman cannot link to the following workstation: "workstation_name".

Explanation

Mailman is trying to link to the workstation: workstation_name and either the writer service on the workstation is unavailable or the version of the HCL Workload Automation at the workstation is not compatible with the version of mailman.

System action

The operation on the workstation is not performed. Mailman proceeds.

Operator response

Verify that the workstation is working correctly. Verify that the version of HCL Workload Automation on the workstation is correct, by issuing the conman command v, or by using the Job Scheduling Console options to determine the version. Look at the stdlist file on the workstation for more information about the possible causes. The file can be found in the directory <InstallDir>\stdlist\logs.

AWSBCV045E   Error adding cpu !1 to Symphony, Error: !2

AWSBCV047E   Error getting info on Sinfonia

AWSBCV048E   Error renaming Sinfonia on !1

AWSBCV050E   Error writing Sinfonia on !1

AWSBCV051E   Error purging Sinfonia on !1

AWSBCV052E   Error closing Sinfonia on !1

AWSBCV053E   Error closing Symphony on !1

AWSBCV054E   Error closing mailbox on !1

AWSBCV057E   Error writing to remote Mailbox on !1

AWSBCV058E   Error opening remote Mailbox on !1

AWSBCV059E   Error building remote Mailbox on !1

AWSBCV060E   Error opening DSline to !1, Type !2, Error !3

AWSBCV062E   Mailman encountered the following error when attempting to open the Symphony file: "error_message".

Explanation

error_message contains the operating system error message.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV063E   Link to !1 failed

AWSBCV064E   Error attempting to lock Links, Error: !1

AWSBCV065E   Error creating Start program !1, Error: !2

AWSBCV066E   Mailman was not able to remove a record from the following message file: "message_file". The following gives more details of the error: "error_message".

Explanation

Mailman encountered an error while rereading a record from the message file before deleting it. Mailman processes message records in the following way:

  1. It reads a record.
  2. It processes the record.
  3. It rereads the record and removes it from the message file.

message_file is the name of the file that mailman is processing. error_message contains the operating system error message.

System action

Mailman stops.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV067E   Mailman was not able to read a message from the following message file in the pobox directory: "message_file". The following gives more details of the error: "error_message"

Explanation

message_file is the name of the file that mailman is processing. error_message contains the operating system error message.

System action

Mailman stops.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV068E   Mailman found a discrepancy when trying to delete a message from the Mailbox.msg message file. The following gives more details of the error: "error_message"

Explanation

Mailman processes record messages in the following way:

  1. It reads a record.
  2. It processes the record.
  3. It rereads the record and removes it from the message file.

Mailman issues this error when the length of the reread record does not match the length of the record when it was first read.

System action

Mailman stops.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV069E   Mailman cannot find the workstation: "workstation_name" in the Symphony file.

Explanation

Mailman cannot find the workstation_name of either the workstation where it is running, or of the master domain manager, in the Symphony file.

System action

Mailman stops.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV076E   Mailman could not add information about the following workstation: "workstation_name" to the Symphony file. The following gives more details of the error: "system_error"

Explanation

Mailman could not write a workstation record in the Symphony file.

workstation_name is the name of the workstation mailman is trying to write a message for. system_error contains the operating system error message.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV078E   Error locking Straus

AWSBCV079E   Error unlocking Straus

AWSBCV080W   Warning link to !1 not found in Straus

AWSBCV081E   Error updating Straus

AWSBCV084E   Mailman could not link to the following workstation "workstation_name" because it encountered a non valid link type: "link_type_ID".

Explanation

Mailman has encountered an unknown link type (it is neither TCP nor DS).

workstation_name is the name of the workstation mailman is trying to link to.

link_type_ID is the actual link type encountered.

System action

Mailman stops.

Operator response

An internal error has occurred. Try to restart mailman. If the error persists, and you are on a fault-tolerant agent or a domain manager, try removing the Symphony file and then relinking to the workstation, using the conman command link <workstation_name>.

The chapter in this guide on 'Symphony file corruption'.

AWSBCV088E   Mailman could not write a mailbox record to the Intercom.msg file. The following gives more details of the error: "error_message".

Explanation

Mailman encountered an error when it tried to write a mailbox record to the Intercom.msg message file.

error_message contains the operating system error message.

System action

Mailman stops. The message it was trying to write could not be sent to batchman. Batchman might not be able to process the Intercom.msg message file.

Operator response

If the operating system error message is not End of file, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

If the operating system error message is End of file, the internal size limit of the file has been reached. In this case, expand the Intercom.msg file using the evtsize utility. To permanently increase the file size, insert an EVSIZE variable set to the desired size in the StartUp command file (before the line that runs netman) in the HCL Workload Automation user home directory.

AWSBCV089E   Error writing to remote !1, Error: !2

AWSBCV095E   Mailman was unable to pass a message to the following mailman server: "server_name" because of the following internal error: "error_message".

Explanation

Messages are passed to a mailman server process by writing mailbox records to its pobox/<server>.msg file. See the server keyword in the workstation definition for an explanation of mailman server processes.

server_name is the name of the mailman server to which the message is sent. error_message describes the error and includes the operating system error message.

System action

Mailman stops.

Operator response

If the operating system error message is not End of file, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

If the operating system error message is End of file, the internal size limit of the has been reached. In this case, expand the pobox/<server>.msg file using the evtsize utility. To permanently increase the file size, insert an EVSIZE variable set to the desired size in the StartUp command file (before the line that runs netman) in the HCL Workload Automation user's home directory.

AWSBCV097E   Mailman cannot access the batchman program file.

Explanation

Mailman cannot access the batchman program file.

System action

Mailman stops. Batchman does not start.

Operator response

Verify in the product's installation directory that an executable called batchman exists, and that it has correct file access permission. If the workstation on which the error occurred is a standard agent or broker workstation, you should look for the executable on its host workstation. If the workstation on which the error occurred is a fault-tolerant agent workstation, or a Master domain manager workstation, you should look for the executable on that same workstation.

If you cannot find the executable, or you find it but the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV098W   Mailman has not received an acknowledgement for a message sent to workstation: "workstation_name".

Explanation

There are two possible reasons:

  • The version of the HCL Workload Automation Agent running on workstation_name is incompatible with the version of mailman.
  • A corruption of the event occurred during the transmission.

System action

Mailman proceeds. No information is lost.

Operator response

To determine the reason and correct the problem, take the following steps:

  1. Verify the version of the agent on the workstation by issuing the conman command v on the workstation, or by checking in the Dynamic Workload Console.
  2. If the version is not compatible with the version of mailman, upgrade the agent or HCL Workload Automation running on the computer where mailman is running (whichever is back-level). See the HCL Workload Automation Planning and Installation Guide for instructions on upgrading the components.
  3. If the agent and mailman are at compatible versions, unlink and relink the workstation using the conman commands unlink <workstation_name> and link <workstation_name>.
  4. If the link command gives an error, investigate and correct the reason for the error and then repeat this step.
  5. Then retry the operation.

AWSBCV099E   Mailman has lost communication with workstation: "workstation_name".

Explanation

The writer of the workstation is not running or is not responding due to communication problems.

workstation_name is the name of the workstation that is not responding to mailman.

System action

Mailman stops.

Operator response

Take the following steps:

  1. Verify that the workstation is available by using the ping command to check both if it is available and if its answer time is acceptable.
  2. If the workstation is available, unlink and relink the workstation using the conman commands unlink <workstation_name> and link <workstation_name>.
  3. If the link command gives an error, investigate and correct the reason for the error and then repeat this step.
  4. Then retry the operation.

AWSBCV100W   Warn: DS remotes are invalid, assuming slave for !1.

AWSBCV101E   Error: TCP slaves are invalid, can not initialize !1.

AWSBCV107E   Mailman has encountered an internal error as it could not find a record for the following workstation in the Symphony file: "workstation_name".

Explanation

See message.

workstation_name is the name of the workstation for which mailman could not find a record.

System action

Mailman might stop, depending on the nature of the error.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV110E   Mailman has verified that jobman has terminated unexpectedly. The exit status of jobman is: "exit_status".

Explanation

This message is issued when a mailman process running on a standard agent or broker workstation determines that jobman on the same workstation has failed.

exit_status contains the jobman exit status.

System action

Mailman may stop, depending on the nature of the error.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV111E   Error setting pgid: !1

AWSBCV112E   Mailman encountered an error trying to start or restart a workstation. The following gives more details of the error: "error_message".

Explanation

See message.

error_message is a message that contains more information about the error and includes the operating system error message, if any.

It is possible that the remote node is not reachable, it is not responding, switched off, or the service is already active or has been disabled. The name of the workstation involved can be determined from associated messages.

System action

Mailman proceeds.

Operator response

Read the error message for more information, then perform the following:

  1. Use the ping command to check the workstation's availability. If it is now available, you can link to it manually, or leave mailman to relink to it automatically.
  2. Verify that netman on the workstation is working, running StartUp on the workstation if it is not.
  3. Verify that netman on the workstation is listening on the specified netman port, by checking that the netman port specified in the database definition is the same as the port specified in the localopts file on the workstation.

If you want to change the frequency with which mailman attempts to relink to the workstation, modify the appropriate parameter in the localopts file.

If you want to attempt to relink manually to the workstation launch the conman command link <workstation_name>.

AWSBCV113E   The master mailman process has terminated unexpectedly because of an internal error.

Explanation

This message is issued by a mailman server process when the parent mailman process has terminated unexpectedly.

System action

The server mailman stops.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV114E   Mailman could not set the termination signal handling routines. The following gives more details of the error: "error_message".

Explanation

As message.

error_message contains the operating system error message.

System action

Mailman stops.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV115E   Mailman is unable to find the new manager workstation: "workstation_name" in the Symphony file. The following gives more details of the error: "error_message".

Explanation

Mailman is processing a switchmgr command, but is unable to find the new manager workstation in the Symphony file.

workstation_name is the name of the new manager workstation. error_message is the operating system error.

System action

Mailman stops.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV117E   Mailman encountered an internal error while attempting to switch domain managers in the following domain: "domain_name"

Explanation

Mailman is processing a switchmgr command, but was unable to switch domain managers.

domain_name is the name of the domain where the switch was taking place.

System action

Mailman stops.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV118E   Mailman encountered an internal error while attempting to update the Symphony file record header during the initialization process.

Explanation

See message.

System action

Mailman stops.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV119E   Mailman encountered an internal error while attempting to find the workstation record for the workstation on which it is running in the Symphony file.

Explanation

See message.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV120E   Mailman encountered an internal error while attempting to find its own domain definition record in the Symphony file.

Explanation

See message.

System action

Mailman proceeds. The operation is not performed.

Operator response

Verify on the master domain manager that the domain entry for the workstation has been correctly defined and added to the plan (in the Symphony file).

  • If it is not defined, define it.
  • If it has not been added to the plan, run or release the JnextPlan.
  • If it has been defined and added to the plan, the Symphony file could be corrupted, and you should search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
The chapter in this guide on 'Symphony file corruption'.

AWSBCV121E   Mailman cannot link to the following workstation: "workstation_name", which is a domain manager but is running a version prior to 6.0.

Explanation

Mailman encountered an error trying to link to a workstation which is not running HCL Workload Automation version 6.0 or later, but is defined as a domain manager. The link is not allowed because it will cause problems in the network.

workstation_name is the name of the workstation mailman is trying to link to.

System action

Mailman proceeds.

Operator response

Install HCL Workload Automation version 6.0 or later on the indicated workstation.

AWSBCV122E   Mailman cannot link to workstation: "workstation_name".

Explanation

There are two possible reasons:

  1. The most probable reason is that the writer on the workstation is at a version prior to 6.0.
  2. The Symphony file could be corrupt.

workstation_name is the name of the workstation mailman is trying to link to.

System action

Mailman proceeds.

Operator response

Verify the version of HCL Workload Automation on the indicated workstation, using the conman v command, or the Job Scheduling Console.

  • If the version is prior to 6.0, install HCL Workload Automation version 6.0 or later on the workstation.
  • If the version is 6.0 or later search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
The chapter in this guide on 'Symphony file corruption'.

AWSBCV124E   Mailman is unable to connect to workstation "workstation_name" using SSL due to an inconsistency in the HCL Workload Automation network configuration.

Explanation

See message. The most common reason for this error is an inconsistent Security Level. For example, the workstation where mailman is running could be enabled for SSL but the target workstation is not. workstation_name is the name of the workstation you cannot connect to.

System action

Mailman proceeds to process other workstations.

Operator response

Verify on the Master Domain Manager the security level of the workstation that has the problem. Enable or disable SSL as appropriate and where appropriate, to ensure that both this workstation and the target workstation have compatible SSL settings.

See the chapter on setting security in the Planning and Installation Guide for more information about SSL.

AWSBCV125E   Mailman could not write to the following ftbox: "ftbox_name" for "workstation_name". The following gives more details of the error: "error_message".

Explanation

This error occurs when the program encounters a problem while writing into an ftbox(ftbox_name) queue. The possible ftbox queues are ftup and ftdown. They are located in the ftbox directory.

ftbox_name is the name of ftbox where mailman is trying to write.

workstation_name is the local workstation.

error_message describes the error and includes the operating system error message.

System action

Mailman stops.

Operator response

Verify that the ftbox directory was correctly created and that it has access rights to the workstation displaying the error. Verify that no program was requesting an exclusive access to that file at the time of the error.

AWSBCV126E   Mailman has stopped the event counter because it received the following error while processing it: "error_message".

Explanation

Due to problems encountered while processing the event counter table, the event counter process was stopped.

error_message describes the error and includes the operating system error message.

System action

Mailman proceeds.

Operator response

Stop and restart mailman.

The event counter troubleshooting section in the product documentation.

AWSBCV127W   Mailman encountered the following error: "error_message" because an event with id-number 0 was sent from the workstation hosting an X-agent.

Explanation

An event with id-number 0 was sent from the workstation hosting an X-agent.

error_message is the error message (often AWSBAT008E).

System action

Mailman proceeds. This situation may inhibit the correct replay of events on this X-agent if a switchmgr command is run later.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

The event counter troubleshooting sectionin the product documentation.

AWSBCV128E   Mailman cannot send an acknowledgement (ACK) to the writer on the following workstation: "workstation_name ".

Explanation

During the replay protocol with the writer on the indicated workstation, mailman could not acknowledge the receipt of a portion of the event counter table from the remote writer.

workstation_name is the name of the remote workstation.

System action

The replay protocol was interrupted. Mailman proceeds.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV129E   Mailman cannot send a message indicating that a communication problem had been encountered (NACK) to the writer on the following workstation: "workstation_name".

Explanation

During the replay protocol with the writer on the indicated workstation, mailman could not communicate that it had encountered a problem while transferring the event counter table from the remote writer.

workstation_name is the name of the remote workstation.

System action

The replay protocol was interrupted. Mailman proceeds.

Operator response

Check if there are any messages in the STDOUT that indicate that the writer at the workstation had a problem when loading the event counter table. If such a message or messages are found, attempt to resolve the problems. If you have resolved these problems, wait for mailman to reattempt to process this workstation, at which point the error should not reoccur.

Otherwise search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV132E   Mailman could not create the replay file for "workstation_name".

Explanation

At the end of the replay protocol, mailman could not create the file (called <workstation_name>_replayed) in the ftbox directory. This file indicates that the replay protocol has been run for that workstation and prevents mailman from rerunning it next time the link is established.

System action

Mailman proceeds.

Operator response

Verify whether there are any problems due to incorrect access rights or disk space that prevent mailman from writing to the ftbox directory. If you find such a problem and fix it, check if the workstation has received the mailman messages. If it has, you can then create the <workstation_name>_replayed file manually.

Otherwise, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV133W   Mailman could not truncate the ftbox "ftbox_name".

Explanation

During plan creation, one or both of the ftbox message files are truncated (the reader and writer pointers to the files are set to the beginning). For some reason mailman cannot perform this task.

System action

Mailman proceeds.

Operator response

Verify that the ftbox directory was correctly created and that it has the correct access rights. Verify that no program was requesting an exclusive access to that file at the time of the error. If you think the error has been resolved, wait for mailman to reattempt the processing of this file, at which point the error should not reoccur.

If you can find no apparent reason for the error, stop mailman, delete the message file that gave the error and restart mailman.

If the error persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV134W   The replay table could not be passed to the following workstation: "workstation_name" because of an internal error.

Explanation

See message.

System action

Mailman proceeds. Linking to the workstation will proceed with a reduced replay protocol.

Operator response

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV135W   Mailman is in isolated state and cannot open any outbound connection.

Explanation

This workstation is an old domain manager that still has to perform the demotion from domain manager to full status fault-tolerant agent. During this phase, the old domain manager must not connect to other agents in the network, so it was restarted in isolated mode.

This warning explains the error that usually precedes it in the log about a failed link attempt.

System action

Mailman proceeds. This state continues until the switchmgr command is processed.

Operator response

Wait for the old domain manager to process the switchmgr command and give up its status of domain manager.

If for urgent reasons the old manager must connect with the rest of the network, stop and restart the agent. It restarts in a non-isolated state.

AWSBCV136W   Event !1 from: !2 to: !3 on iteration !4 was canceled.

AWSBCV137W   A possible message loss was detected at the start of the replay protocol on the following event: "record_ID", from the following workstation: "workstation_name".

Explanation

This warning indicates a potential loss of a message during the replay protocol. After exchanging the counter table, the first message drawn from the fault tolerance queue (ftbox) is passing through the filter, indicating that maybe other previous messages were lost. This warning might appear after the switchmgr command has been run.

If this warning occurs after JnextPlan, this is a normal condition. If it occurs during the day, it may indicate that one or both of the ftbox message files have reached their size limit, and it is probable that one or more messages have been lost.

record_ID is a number that identifies the event. workstation_name is the remote workstation name.

System action

Mailman proceeds.

Operator response

If the warning did not follow JnextPlan, check on the state of the jobs run on the workstation displaying the warning or on other workstations under it in the hierarchy. If you think that messages have been lost, expand the ftbox message files using the evtsize utility. To permanently increase the file size, insert an EVSIZE variable set to the desired size in the StartUp command file (before the line that runs netman) in the HCL Workload Automation user's home directory.

AWSBCV139E   An internal error has occurred while updating the Mailbox header. The error message is as follows: "error_message".

Explanation

See message.

error_message is a message that contains information about the error and includes the operating system error message.

System action

Mailman stops.

Operator response

Attempt to resolve the operating system error. Restart mailman.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBCV140W   An error has occurred while creating the Windows event object which signals the status of the HCL Workload Automation processes. The error message is as follows: "error_number".

Explanation

Mailman creates a Windows event object if the workstation instance is being used in a Microsoft Cluster Environment. The object is used to signal the status of the HCL Workload Automation processes. The creation of this object has failed. This means that mailman will not be able to signal the status of the processes. For example, it will not be able to signal that a conman stop command has been launched.

error_number is the operating system error number.

System action

Mailman proceeds.

If you take no corrective action, mailman might continue to work successfully. However, to maintain full control of the workstation in the cluster environment you are recommended to correct the problem.

Operator response

Attempt to resolve the operating system error. Restart mailman.

AWSBCV143E   Mailman encountered an error trying to send switchmgr command to a workstation. The following gives more details of the error: "error_message".

Explanation

See message.

error_message is a message that contains more information about the error and includes the operating system error message, if any.

It is possible that the remote node is not reachable, it is not responding, switched off, or the service has been disabled. The name of the workstation involved can be determined from associated messages.

System action

Mailman proceeds.

Operator response

Read the error message for more information, then perform the following:

  1. Use the ping command to check the workstation's availability. If it is now available, you can link to it manually, or leave mailman to relink to it automatically. As soos as the workstation is linked, you can rerun the switchmgr command.
  2. Verify that netman on the remote workstation is working, running StartUp on the workstation if it is not.
  3. Verify that netman on the workstation is listening on the specified netman port, by checking that the netman port specified in the database definition is the same as the port specified in the localopts file on the workstation.
  4. Check if a firewall is present between this workstation and the remote one.Verify that port where netman is listening on the remote workstation is opened on the firewall.

If you want to attempt to relink manually to the workstation launch the conman command link <workstation_name>. As soos as the workstation is linked, you can rerun the switchmgr command.

AWSBCV144E   Mailman could not write a mailbox record to the auditbox.msg file. The following message contains more details of the error: "error_message".

Explanation

Mailman encountered an error while trying to write a mailbox record to the auditbox.msg message file.

error_message contains the operating system error message.

System action

Mailman stops. The message was not sent to the audit monitor. The audit monitor might not be able to process the auditbox.msg message file.

Operator response

If the operating system error message is not End of file, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

If the operating system error message is End of file, the internal size limit of the file has been reached. In this case, expand the auditbox.msg file using the evtsize utility. To permanently increase the file size, insert an EVSIZE variable set to the appropriate size in the StartUp command file (before the line that runs netman) in the HCL Workload Automation user home directory.

Parent topic: HCL Workload Automation messages