LIBTG Messages 1000-1099

1000

ERROR: config file <val> not found

Description

The BEA TUXEDO/BEA TOP END gateway configuration file was not found. (This file is specified with the -f parameter-on the CLOPT line for the gateway-in the SERVERS section of ubbconfig.)

Action

Create a configuration file (if one does not exist) and set the -f (CLOPT) parameter.

1001

WARN: unknown section <val> in val - skipping

Description

Valid sections for the gateway configuration file are:

• TE_LOCAL_SERVICES
• TE_REMOTE_SERVICES

  Any o ther sections are ignored.

Action

The system ignores the line containing the name of the invalid section. If this behavior is acceptable, then no action is required. (Even if it is acceptable for this line to be ignored, however, it is a good idea to delete it to maintain a clean file.)

If the name is invalid because of a spelling or typing error, then correct the error.

1002

ERROR: service name <val> too long, max val characters

Description

The service name specified in the service definition file (as specified by the -fCLOPT parameter) contains more than the maximum number of characters supported by the BEA TUXEDO system. The gateway will exit gracefully.

Action

Modify the service names in the configuration file and re-boot the gateway.

1003

ERROR: syntax error in configuration file: <val>

Description

A syntax error was detected in the service definition file specified by the -f CLOPT parameter. The gateway will exit gracefully.

Action

Fix the indicated line and re-boot the gateway.

1004

ERROR: product name <val> too long, max val characters

Description

The product name specified in the service definition file (as specified by the -fCLOPT parameter) contains more than the maximum number of characters supported by BEA TOP END. The gateway will exit gracefully.

Action

Modify the product names in the configuration file and re-boot the gateway.

1005

ERROR: function name <val> too long, max val characters

Description

The function name specified in the service definition file (as specified by the -fCLOPT parameter) contains more than the maximum number of characters supported by BEA TOP END. The gateway will exit gracefully.

Action

Modify the function names in the configuration file and re-boot the gateway.

1006

ERROR: target name <val> too long, max val characters

Description

The target name specified in the service definition file (as specified by the -fCLOPT parameter) contains more than the maximum number of characters supported by BEA TOP END. The gateway will exit gracefully.

Action

Modify the target names in the configuration file and re-boot the gateway.

1007

ERROR: unknown tag <val> in val

Description

An unknown tag was found in the service definition file specified by the -f CLOPT parameter. The gateway will exit gracefully.

Action

Correct the configuration file and re-boot the gateway.

1008

ERROR: exceeded number of entries (val) supported by gateway

Description

The service definition file (specified by the -fCLOPT parameter) contains more entries than can be supported by the gateway. The gateway will exit gracefully.

Action

Ei ther remove service entries from the configuration file, or configure a second gateway (with a second configuration file) and segment the services.

1009

ERROR: service <val> does not have PRODUCT defined in file val

Description

PRODUCT is a mandatory field. It must be specified, either on the DEFAULT: line or in each service entry.

Action

Add product names as appropriate and re-boot the gateway.

1010

ERROR: multiple product names not allowed in TE_LOCAL_SERVICES section

Description

The GWTE2TUX gateway supports a single product name. All service entries in the TE_LOCAL_SERVICES section must have the same product name.

Action

Modify the file so that all product names in the LOCAL_SERVICES section are the same. If multiple products are needed, use an additional configuration file to configure a second gateway with a different product name.

1011

WARN: Unable to establish connection to TOP END

Description

Th egateway was unable to connect to the BEA TOP END system. The gateway needs to connect to a BEA TOP END Network Agent.

Action

Make sure that the BEA TOP END Network Agent (NA) is running and configured properly. Also make sure that the BEA TOP END remote configuration file (as specified by the -cCLOPT parameter, or topendrc.cfg by default) is configured with the proper BEA TOP END system, machine, and port number.

1012

ERROR: Cannot allocate TOP END client DIF structure

Description

The gateway was unable to allocate the memory needed for BEA TOP END communication. The gateway will retry the allocation as specified by the -RCLOPT parameter.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1013

ERROR: Sign on to TOP END failed. Error code=val(val). server exiting...

Description

The GWTUX2TE gateway issued a call to tp_client_signon (to sign on to the BEA TOP END system) and the call failed.

Action

Check the description of the error code available in the tp_client_signon(3T) entry in the BEA TOP END Reference Manual.

1014

ERROR: username and password (-u and -p) invalid or not specified

Description

The GWTUX2TE gateway has invalid credentials and has failed BEA TOP END au thentication.

Action

Modify the user name or password (using the -u or -p parameter, respectively), or add the user_ID/password combination to the BEA TOP END security database.

1015

ERROR: failed on TOP END receive during initialization. Error code=val(val)

Description

The GWTUX2TE gateway failed to receive a response from BEA TOP END for the call to tp_client_signon.

Action

Check the description of the error code available in the tp_client_receive(3T) entry in the BEA TOP END Reference Manual.

1016

ERROR: failed on TOP END send. retcode=val(val) extended status=val(val)

Description

The GWTUX2TE gateway was unable to send the message to the BEA TOP END system.

Action

Check the description of the error code available in the tp_client_send(3T) entry in the BEA TOP END Reference Manual.

1017

ERROR: failed on TOP END receive. retcode=val(val) extended status=val

Description

The GWTUX2TE gateway was unable to receive a response from the BEA TOP END system.

Action

Check the description of the error code available in the tp_client_receive(3T) entry in the BEA TOP END Reference Manual.

1018

WARN: TOP END server sent response with TP_APPL_CONTEXT. Resetting dialog

Description

The BEA TOP END server set the TP_APPL_CONTEXT flag with the response. This flag is not supported by the gateway. The gateway sent an error back to the server and reset the dialog. The gateway can continue processing.

Action

The TP_APPL_CONTEXT flag is not supported by the gateway. The application should be modified so that the flag is not set.

1019

INFO: stale response message received from TOP END - ignoring

Description

The response that was received is apparently an orphaned response. This problem can occur when the gateway goes down and restarts. The gateway continues to search for the matching response.

Action

No action is required.

1020

ERROR: TOP END initialization Failed. Error code=val(val)

Description

The GWTUX2TE gateway failed on the call to tp_initialize.

Action

Check the description of the error code available in the tp_initialize(3T) entry in the BEA TOP END Reference Manual.

1021

ERROR: service definition file (-f )not specified. Exiting server...

Description

The -f parameter is required in the list of CLOPT options for the gateway.

Action

Add the -f parameter to the list of CLOPT options for the gateway and re-boot the BEA TUXEDO system.

1022

ERROR: cannot access MIB for security info. val. Exiting server...

Description

The -u and -g parameters were specified for the gateway. The gateway needs to perform a MIB look-up to obtain the appropriate security credentials. The MIB request failed.

Action

Verify that the TMIB service is advertised.

1023

ERROR: cannot access MIB for security info. val. Exiting server...

Description

The -u and -g parameters were specified for the gateway. The gateway needs to perform a MIB look-up to obtain the appropriate security credentials. The MIB request failed.

Action

Verify that the TMIB service is advertised.

1024

ERROR: unable to allocate TOP END receive buffer. Exiting server...

Description

The gateway was unable to allocate the memory needed for BEA TOP END communication.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1026

ERROR: TOP END tp_csi_alloc Failed. Exiting server...

Description

The gateway was unable to allocate the memory needed for BEA TOP END communication.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1027

ERROR: function name not found

Description

The GWTE2TUX gateway received a BEA TOP END client request with a function name that is not recognized by the gateway. The gateway sent an error to the client. It will continue processing.

Action

Check the service definition file to verify the function names.

1028

ERROR: failed to convert message to TUXEDO format

Description

The gateway was unable to convert the BEA TOP END client request into the BEA TUXEDO buffer format.

Action

Check the message in the userlog preceding this message for fur ther information. Possible symptoms are: message too large (max 30K), unsupported BEA TUXEDO buffer type.

1029

ERROR: failure attempting to reach service name (name)

Description

The GWTE2TUX gateway was unable to reach the specified BEA TUXEDO service. The specific error is indicated in paren theses.

Action

Probable causes are: the service is not advertised or is suspended, or the service name advertised by the BEA TUXEDO system (as specified in the SERVICES section of ubbconfig) does not match the service name in the gateway's service definition file. Make sure the service is advertised and the service names in ubbconfig and the service definition file match. Also check the error value in tpacall(3c).

1030

ERROR: failure attempting to get reply from service name (name)

Description

The GWTE2TUX gateway was unable to receive a response from the BEA TUXEDO service. The specific error is indicated in paren theses.

Action

Check the error value in tpgetrply(3c).

1031

ERROR: failed to convert message to TOP END format

Description

The gateway was unable to convert the BEA TUXEDO server response into the BEA TOP END buffer format.

Action

Check the message in the userlog preceding this message for fur ther information. Possible symptoms are: message too large (max 30K), unsupported BEA TUXEDO buffer type.

1032

ERROR: tp_server_send failed with unknown TOP END code[name]

Description

The gateway received an unknown receive code from the tp_server_send() call. The gateway will continue to process messages.

Action

No action is required.

1033

ERROR: tp_server_send failed with unknown TOP END code[name]

Description

The gateway received an unknown receive code from the tp_server_send() call. The gateway will continue to process messages.

Action

No action is required.

1034

ERROR: Conversational services not supported by gateway

Description

The gateway does not support conversation services (tpconnect, tpsend, and tprecv).

Action

BEATUXEDO clients and servers should be built to use the request/response paradigm.

1035

ERROR: transactions not supported by gateway

Description

The gateway does not support transactions (tpbegin and tpcommit).

Action

The client call to the BEA TOP END service should include the TPNOTRAN flag.

1037

ERROR: Tuxedo->TopEnd service mapping not found for service name

Description

The name of the BEA TUXEDO service specified in the error message is not included in the table for the GWTUX2TE gateway.

Action

Check the service definition file for the gateway to see if it includes an entry for the service name.

1038

ERROR: invalid value specified for wait time (-w), Server exiting...

Description

The wait time must be greater than or equal to 0.

Action

Modify the wait time to a valid value.

1039

ERROR: can't open password file <name>, fopen errno=val. Server exiting

Description

The password file (specified by the -p CLOPT parameter) cannot be accessed. Possible causes are: the file does not exist, or the permissions are not valid.

Action

Ensurethat the file exists and is readable by the BEA TUXEDO administrator.

1040

ERROR: service definition file (-f )not specified. Server exiting...

Description

The -f parameter is required in the list of CLOPT options for the gateway.

Action

Add the -f parameter to the list of CLOPT options for the gateway and re-boot the BEA TUXEDO system.

1041

ERROR: Config file (-f ) not specified, server exiting

Description

The -f parameter is required in the list of CLOPT parameters for the gateway.

Action

Add the -f parameter to the list of CLOPT options for the gateway and re-boot the BEA TUXEDO system.

1042

ERROR: unable to allocate TOP END receive buffer

Description

The gateway was unable to allocate the memory needed for BEA TOP END communication.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1043

INFO: retrying connection to TOP END every val seconds

Description

The gateway was unable to connect to BEA TOP END; it will perform periodic retries. The gateway will not advertise remote services until a connection is established.

Action

No action is required.

1044

INFO: connection established to TOP END

Description

The gateway has successfully connected to BEA TOP END.

Action

No action is required.

1045

WARN: Network connection closed by TOP END

Description

The network connection has been closed for one of the following reasons: the BEA TOP END system was shut down, the NA was shut down, or the network connection was broken.

Action

If you have planned this downtime, no action is required. If you have not planned this downtime, check the BEA TOP END system and bring it up if necessary. Also check network connectivity.

1046

WARN: Network connection closed by TOP END

Description

The network connection has been closed for one of the following reasons: the BEA TOP END system was shut down, the NA was shut down, or the network connection was broken.

Action

If you have planned this downtime, no action is required. If you have not planned this downtime, check the BEA TOP END system and bring it up if necessary. Also check network connectivity.

1047

WARN: Network connection closed by TOP END

Description

The network connection has been closed for one of the following reasons: the BEA TOP END system was shut down, the NA was shut down, or the network connection was broken.

Action

If you have planned this downtime, no action is required. If you have not planned this downtime, check the BEA TOP END system and bring it up if necessary. Also check network connectivity.

1048

WARN: Network connection closed by TOP END

Description

The network connection has been closed for one of the following reasons: the BEA TOP END system was shut down, the NA was shut down, or the network connection was broken.

Action

If you have planned this downtime, no action is required. If you have not planned this downtime, check the BEA TOP END system and bring it up if necessary. Also check network connectivity.

1049

ERROR: function <val: default from service> too long, max val chars

Description

The BEA TOP END function name defaults to the BEA TUXEDO service name. The number of characters in the BEA TUXEDO service name does not exceed the number allowed for service names, but it does exceed the number of characters allowed for function names.

Action

Adda function name that contains no more than eight characters to the service definition file and re-boot the gateway.

1050

WARN: unable to connect to TOP END system and retry option is disabled. Exiting server...

Description

The -R parameter was specified as 0 in the CLOPT entry for the gateway. The gateway may restart and attempt to connect again (if it has been configured for restart).

Action

No action is required.

1051

WARN: unsupported command-line option val

Description

The option specified in the CLOPT line for the gateway is not recognized. The gateway ignores it.

Action

No action is required.

1052

ERROR: call to tgAllocTuxedoBuffer failed

Description

The gateway was unable to allocate the memory needed for BEA TUXEDO communication.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1053

ERROR: call to tgConvertMessage failed TUX2TE incoming

Description

The gateway was unable to convert the BEA TUXEDO client request into the BEA TOP END buffer format.

Action

Check the message in the userlog preceding this message for fur ther information. Possible symptoms are: message too large (max 30K), unsupported BEA TUXEDO buffer type.

1054

ERROR: call to tgConvertMessage failed TUX2TE outgoing

Description

The gateway was unable to convert the BEA TOP END server response into the BEA TUXEDO buffer format.

Action

Check the message in the userlog preceding this message for fur ther information. Possible symptoms are: message too large (max 30K), unsupported BEA TUXEDO buffer type.

1055

ERROR: no service mappings defined in file name

Description

Noentries for the gateway are included in the service definition file. For the GWTE2TUX gateway, there are no entries in the TE_LOCAL_SERVICES section. For the GWTUX2TE gateway, there are no entries in the TE_REMOTE_SERVICES section.

Action

Add service entries for the gateway.

1056

INFO: TOP END admin message: name

Description

A BEA TOP END administrative message was sent to the gateway.

Action

No action is required.

1057

WARN: error while processing TOP END admin message [name,name]

Description

A BEA TOP END administrative message was sent to the gateway and an error occurred in the tp_system_admin() call.

Action

No action is required.

1058

ERROR: tp_server_send failed [name,name], ext_status=[name,name]

Description

The GWTE2TUX gateway failed an attempt to send the response to the BEA TOP END client. The gateway will continue to process messages.

Action

Check the description of the error code available in the tp_server_send(3T) entry in the BEA TOP END Reference Manual.