AWSBHX - Logman messages

This section lists error and warning messages that might be issued by logman.

The message component code is BHX.

AWSBHX011W

The job has negative elapsed time. Check the time parameters.

AWSBHX021E

An error occurred opening the temporary file "file_name".

See message.

file_name is the file that cannot be opened.

Logman stops.

Check the following:

  • That the file exists
  • That the file is in the correct directory
  • That the file has read permission
  • That there is sufficient disk space to open and read a file
  • That there are sufficient file descriptors available to open a file.

Correct any errors that you find, and restart logman.

AWSBHX022E

An internal error occurred while initializing the HTTP communication. The library returned this error "error_message".

See message.

error_message is the reason for the error returned by the library.

Logman 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.

AWSBHX023E

An internal error occurred while sending data to the server. The error message is "error_message".

See message.

error_message is the reason for the error.

Logman 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.

AWSBHX024E

An internal error has occurred. The server has returned an error code. RC="server_return_code"

See message.

server_return_code is the return code returned by the server.

Logman 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.

AWSBHX027W

The value specified for the -timeout connection parameter is not valid. It must be the number of seconds that the command line client is to wait for a connection before timing out.

The -timeout parameter is one of the connection parameters. These are supplied: as part of the command, in a file of connection parameters, or by default from the useropts or localopts file. It must be expressed as a number (of seconds). For example, the value for 30 seconds must be 30, not 30s or 30 secs.

The operation is not performed.

Retry the command, changing the value of the timeout parameter to be a number of seconds.

AWSBHX032W

The job with Workstation: "workstation" Job Name: "job_name" has a null started date. For this reason, it doesn't appear in any collected statistics.

The job, even if completed, contains a NULL started date. It is skipped in the statistics calculation.

The operation is not performed.

AWSBHX033W

The count of jobs cannot be performed on the current production Symphony file.

The count of jobs can be performed only on a Symphony file different from the current one.

The operation is not performed if the -jobcountonly parameter is specified and skipped otherwise.