AWSBJG - Router messages

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

The message component code is BJG.

AWSBJG001E

Router cannot initialize the communication or set the connection type and file descriptor for the connected socket to make an SSL connection to conman. The following error message is given: "error_message"

error_message is the operating system error message text.

Router stops and the operation fails.

Check that the network is working correctly. Check that SSL is configured correctly. If you have corrected the error, use the workstation stop and start commands to restart router.

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

AWSBJG002E

Router is unable to create the stdlist file.

See message.

Router stops and the operation fails.

Check the file system of the <TWS_home> directory to ensure that there is sufficient space, and that the user has write permission. If you have corrected the error, use the workstation stop and start commands to restart router.

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

AWSBJG004W

Warning illegal timeout value: !1, using default

AWSBJG005E

Router has been invoked with an incorrect number of arguments.

If you have invoked router manually, you have not supplied the correct number of arguments.

If router has been invoked by a HCL Workload Automation process, this is an internal error.

Router does not start.

If you have invoked router manually, check the syntax by issuing the command with just the -u argument (router -u). Retry the operation.

If router has been invoked by a HCL Workload Automation process, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBJG006E

Router cannot perform the data translation between network format and host format required for SSL communication. (ntoh). The following error message is given: "error_message"

error_message either identifies the record that could not be translated or gives more information about the error.

Router stops and the operation fails.

This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBJG007E

Router cannot send router packets on the network. The following error message is given: "error_message"

error_message either identifies the record that could not be sent or gives more information about the error.

Router stops and the operation fails.

Check that the network is working correctly. If you have corrected the error, use the workstation stop and start commands to restart router.

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

AWSBJG008E

Router cannot receive router packets from the network. The following error message is given: "error_message"

error_message either identifies the record that could not be received or gives more information about the error.

Router stops and the operation fails.

Check that the network is working correctly. If you have corrected the error, use the workstation stop and start commands to restart router.

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

AWSBJG009E

Router ran out of memory allocating memory for internal data structures (comarea).

See message.

Router stops and the operation is not performed.

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 might need to increase the memory of the workstation or make changes in memory management and paging to make more memory available to router. Use the workstation stop and start commands to restart router.
  2. If the workstation memory is adequate, try closing all the applications that you do not need, and then use the workstation stop and start commands to restart router.
  3. If the problem persists, reboot the workstation, and then use the workstation start command to restart router.
  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.

AWSBJG011E

Scribner, called by router, cannot read the standard list file (stdlist) for the following job: "workstation_name"."job_stream_name": "job_name"

workstation_name, job_stream_name, and job_name identify the job for which the standard list could not be read.

Router stops and the operation is not performed.

Verify if the standard list file exists and has read permission for the <TWS_user>.

Check if there are any network problems that might prevent scribner from accessing the workstation where the job was running.

If you have solved the problem, use the workstation stop and start commands to restart router.

AWSBJG012E

Router cannot open or read the Symphony file.

See message.

Router stops and the operation is not performed.

Verify if the Symphony file exists and has read permission for the <TWS_user>.

If you have solved the problem, use the workstation stop and start commands to restart router.

AWSBJG015E

The following error occurred opening the configuration file "file_name": "error_message".

See message.

Router stops and the operation is not performed.

Verify whether the configuration file exists and has read permission for the <TWS_user>.

AWSBJG016E

An error occurred reading the configuration file "file_name": "error_message".

See message.

Router stops and the operation is not performed.

Verify whether the configuration file exists and has read permission for the <TWS_user>.

AWSBJG017E

An error occurred while closing the configuration file "file_name": "error_message".

See message.

Router stops and the operation is not performed.

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