LIBGW MESSAGES 4000 & Above

LIBGW MESSAGES 4000-4099

4019 ERROR: Cannot get fieldid for fld

DESCRIPTION

A system error occurred in getting the field identifier when loading the routing entry into the Bulletin Board.

ACTION

Check the field tables to see if the field specified in the routing table is defined. Also, check your environment variables FLDTBLDIR and FIELDTBLS.

SEE ALSO

DMCONFIG (5)

4023 ERROR: unknown type type to route on

DESCRIPTION

The BUFTYPE, type, for routing is unknown to the system. Currently, only VIEW and FML are supported buffer types for routing.

ACTION

Check your BUFTYPE definitions in the *DM_ROUTING section of the DMCONFIG file. Only VIEW and FML can be specified. Then, re-load the BDMCONFIG file and re-boot the application.

SEE ALSO

DMCONFIG (5)

4024 ERROR: cannot use data, field type not identical for field fieldname

DESCRIPTION

The data routing entry cannot be used because the field type is not identical for field, fieldname, in the routing table.

ACTION

Check the field type, fieldname, in the *DM_ROUTING section of the DMCONFIG file for consistency.

SEE ALSO

DMCONFIG (5)

4025 ERROR: Can't add ROUTSTRPOOL entry into table

DESCRIPTION

The GWADM administrative server couldn't successfully add a *DM_ROUTING entry into shared memory. Check the surrounding messages for specifics.

ACTION

Correct the error and re-boot the application.

SEE ALSO

DMCONFIG (5)

4026 ERROR: Can't find ROUTSTRPOOL entry in table

DESCRIPTION

The GWADM administrative server couldn't successfully add a *DM_ROUTING entry into shared memory. The server couldn't retrieve the entry it just added.

ACTION

Contact your TUXEDO System Technical Support.

SEE ALSO

DMCONFIG (5)

4027 ERROR: Can't add ROUTSTRPOOL entry into table

DESCRIPTION

The GWADM administrative server couldn't successfully add a *DM_ROUTING entry into shared memory. Check the surrounding messages for specifics.

ACTION

Correct the error and re-boot the application.

SEE ALSO

DMCONFIG (5)

4028 ERROR: Can't find ROUTSTRPOOL entry in table

DESCRIPTION

The GWADM administrative server couldn't successfully add a *DM_ROUTING entry into shared memory. The server couldn't retrieve the entry it just added.

ACTION

Contact your TUXEDO System Technical Support.

SEE ALSO

DMCONFIG (5)

4029 ERROR: Can't add RANGES entry into table

DESCRIPTION

The GWADM administrative server couldn't successfully add a *DM_ROUTING entry into shared memory. Check the surrounding messages for specifics.

ACTION

Correct the error and re-boot the application.

SEE ALSO

DMCONFIG (5)

4030 ERROR: Can't find RANGES entry in table

DESCRIPTION

The GWADM administrative server couldn't successfully add a *DM_ROUTING entry into shared memory. The server couldn't retrieve the entry it just added.

ACTION

Contact your TUXEDO System Technical Support.

SEE ALSO

DMCONFIG (5)

4031 ERROR: dmroute failed, could not find routing criteria of routing_name for buffer type FML

DESCRIPTION

A routing_name was specified for a *DM_REMOTE_SERVICES entry in the DMCONFIG file that does not appear in the *DM_ROUTING section, and the standard FML routing function is used (which requires a matching *DM_ROUTING entry).

ACTION

Correct and re-load the DMCONFIG file, or provide an application-specific routing function for FML typed buffers.

SEE ALSO

DMCONFIG (5)

4032 ERROR: dmroute failed, could not find routing criteria of routing_name for buffer type FML

DESCRIPTION

A routing_name was specified for a *DM_REMOTE_SERVICES entry in the DMCONFIG file that does not appear in the *DM_ROUTING section, and the standard FML routing function is used (which requires a matching *DM_ROUTING entry).

ACTION

Correct and re-load the DMCONFIG file, or provide an application-specific routing function for FML typed buffers.

SEE ALSO

DMCONFIG (5)

4033 ERROR: dmroute failed, could not find routing criteria of routing_name for buffer type VIEW

DESCRIPTION

A routing_name was specified for a *DM_REMOTE_SERVICES entry in the DMCONFIG file that does not appear in the *DM_ROUTING section, and the standard VIEW routing function is used (which requires a matching *DM_ROUTING entry).

ACTION

Correct and re-load the DMCONFIG file, or provide an application-specific routing function for VIEW typed buffers.

SEE ALSO

DMCONFIG (5)

4034 ERROR: dmroute failed, could not find routing criteria of routing_name for buffer type VIEW

DESCRIPTION

A routing_name was specified for a *DM_REMOTE_SERVICES entry in the DMCONFIG file that does not appear in the *DM_ROUTING section, and the standard VIEW routing function is used (which requires a matching *DM_ROUTING entry).

ACTION

Correct and re-load the DMCONFIG file, or provide an application-specific routing function for VIEW typed buffers.

SEE ALSO

DMCONFIG (5)

4035 ERROR: unknown field type used for FML routing

DESCRIPTION

During data-dependent routing of an FML typed buffer, an unknown field type was encountered for the routing field. This should not occur during normal system operation.

ACTION

Contact your TUXEDO System Technical Support.

SEE ALSO

DMCONFIG (5)

4036 ERROR: unknown field type used for VIEW routing

DESCRIPTION

During data-dependent routing of a VIEW typed buffer, an unknown field type was encountered for the routing field. This should not occur during normal system operation.

ACTION

Contact your TUXEDO System Technical Support.

SEE ALSO

DMCONFIG (5)

4037 ERROR: Routing field value for 'service' not valid

DESCRIPTION

While doing data-dependent routing on an FML typed buffer for the specified service service, the routing field value did not match any of the ranges specified in the routing criteria and the criteria did not contain a wild-card pattern.

ACTION

Make sure the routing field value is valid. Correct the routing criteria in the RANGES value of the DMCONFIG file.

SEE ALSO

DMCONFIG (5)

4038 ERROR: Routing field value for 'service' not valid

DESCRIPTION

While doing data-dependent routing on a VIEW typed buffer for the specified service service, the routing field value did not match any of the ranges specified in the routing criteria and the criteria did not contain a wild-card pattern.

ACTION

Make sure the routing field value is valid. Correct the routing criteria in the RANGES value of the DMCONFIG file.

SEE ALSO

DMCONFIG (5)

4039 ERROR: more than one wild card in entry range

DESCRIPTION

More than one wild-card (*) range for the short routing data was specified in the data routing entry.

ACTION

Check your DMCONFIG file for multiple definitions of wild-card ranges for the short routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).

SEE ALSO

DMCONFIG (5)

4040 ERROR: range values out of order upper_range < low_range

DESCRIPTION

The range values for the short routing data are out of order, that is, the upper range is less than the lower range value.

ACTION

Check routing range values for the short routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.

SEE ALSO

DMCONFIG (5)

4041 ERROR: more than one wild card in entry range

DESCRIPTION

More than one wild-card (*) range for the integer routing data was specified in the data routing entry.

ACTION

Check your DMCONFIG file for multiple definitions of wild-card ranges for the integer routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).

SEE ALSO

DMCONFIG (5)

4042 ERROR: range values out of order upper_range < low_range

DESCRIPTION

The range values for the integer routing data are out of order, that is, the upper range is less than the lower range value.

ACTION

Check routing range values for the integer routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.

SEE ALSO

DMCONFIG (5)

4043 ERROR: more than one wild card in entry range

DESCRIPTION

More than one wild-card (*) range for the long routing data was specified in the data routing entry.

ACTION

Check your DMCONFIG file for multiple definitions of wild-card ranges for the long routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).

SEE ALSO

DMCONFIG (5)

4044 ERROR: range values out of order upper_range < low_range

DESCRIPTION

The range values for the long routing data are out of order, that is, the upper range is less than the lower range value.

ACTION

Check routing range values for the long routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.

SEE ALSO

DMCONFIG (5)

4045 ERROR: more than one wild card in entry range

DESCRIPTION

More than one wild-card (*) range for the float routing data was specified in the data routing entry.

ACTION

Check your DMCONFIG file for multiple definitions of wild-card ranges for the float routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).

SEE ALSO

DMCONFIG (5)

4046 ERROR: range values out of order upper_range < low_range

DESCRIPTION

The range values for the float routing data are out of order, that is, the upper range is less than the lower range value.

ACTION

Check routing range values for the float routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.

SEE ALSO

DMCONFIG (5)

4047 ERROR: more than one wild card in entry range

DESCRIPTION

More than one wild-card (*) range for the double routing data was specified in the data routing entry.

ACTION

Check your DMCONFIG file for multiple definitions of wild-card ranges for the double routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).

SEE ALSO

DMCONFIG (5)

4048 ERROR: range values out of order upper_range < low_range

DESCRIPTION

The range values for the double routing data are out of order, that is, the upper range is less than the lower range value.

ACTION

Check routing range values for the double routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.

SEE ALSO

DMCONFIG (5)

4049 ERROR: more than one wild card in entry range

DESCRIPTION

More than one wild-card (*) range for the char routing data was specified in the data routing entry.

ACTION

Check your DMCONFIG file for multiple definitions of wild-card ranges for the char routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).

SEE ALSO

DMCONFIG (5)

4050 ERROR: char range with MAX as lower value has values out of order

DESCRIPTION

If MAX is specified for the char lower routing range, then its corresponding upper routing range must also be specified as MAX, that is, MAX-MAX:remote_domain_name.

ACTION

Check the char routing range in the *DM_ROUTING section of the DMCONFIG file. If MAX is specified for the lower range, then its corresponding upper range must be MAX.

SEE ALSO

DMCONFIG (5)

4051 ERROR: char range with MIN as upper value has values out of order

DESCRIPTION

If MIN is specified for the char lower routing range, then its corresponding upper routing range must also be specified as MIN, that is, MIN-MIN:remote_domain_name.

ACTION

Check the char routing range in the *DM_ROUTING section of the DMCONFIG file. If MIN is specified for the lower range, then its corresponding upper range must be MIN.

SEE ALSO

DMCONFIG (5)

4052 ERROR: range values out of order upper_range < low_range

DESCRIPTION

The range values for the char routing data are out of order, that is, the upper range is less than the lower range value.

ACTION

Check routing range values for the char routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.

SEE ALSO

DMCONFIG (5)

4053 ERROR: more than one wild card in entry range

DESCRIPTION

More than one wild-card (*) range for the string routing data was specified in the data routing entry.

ACTION

Check your DMCONFIG file for multiple definitions of wild-card ranges for the string routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).

SEE ALSO

DMCONFIG (5)

4054 ERROR: range values out of order for the string routing data

DESCRIPTION

The range values for the string routing data are out of order, that is, the upper range is less than the lower range value.

ACTION

Check routing range values for the string routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.

SEE ALSO

DMCONFIG (5)

4055 ERROR: more than one wild card in entry range

DESCRIPTION

More than one wild-card (*) range for the carray routing data was specified in the data routing entry.

ACTION

Check your DMCONFIG file for multiple definitions of wild-card ranges for the carray routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).

SEE ALSO

DMCONFIG (5)

4056 ERROR: range values out of order for the carray routing data

DESCRIPTION

The range values for the carray routing data are out of order, that is, the upper range is less than the lower range value.

ACTION

Check routing range values for the carray routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.

SEE ALSO

DMCONFIG (5)

4057 ERROR: more than one wild card in entry range

DESCRIPTION

More than one wild-card (*) range for the decimal routing data was specified in the data routing entry.

ACTION

Check your DMCONFIG file for multiple definitions of wild-card ranges for the decimal routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).

SEE ALSO

DMCONFIG (5)

4058 ERROR: range values out of order for the decimal routing data

DESCRIPTION

The range values for the carray routing data are out of order, that is, the upper range is less than the lower range value.

ACTION

Check routing range values for the carray routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.

SEE ALSO

DMCONFIG (5)

4059 ERROR: unknown field type given

DESCRIPTION

An unknown field type was specified in the data routing entry.

ACTION

Check the field types specified in the *DM_ROUTING section of the DMCONFIG file.

SEE ALSO

DMCONFIG (5)

4060 ERROR: expected colon to separate remote domain name range

DESCRIPTION

Within a range and a remote domain pair, the range is separated from the remote domain name by a colon (:) in the *DM_ROUTING section of the DMCONFIG file.

ACTION

Check the range and remote domain name specified in the *DM_ROUTING section of the DMCONFIG file. A colon (:) is expected to separate the range and the remote domain name.

SEE ALSO

DMCONFIG (5)

4061 ERROR: expected comma after remote domain name domain_name,string

DESCRIPTION

Within a range and a remote domain name pair, a comma (,) is expected after remote domain name in the *DM_ROUTING section of the DMCONFIG file.

ACTION

Check the range and remote domain name specified in the *DM_ROUTING section of the DMCONFIG file. A comma (,) is expected after the remote domain name.

SEE ALSO

DMCONFIG (5)

4062 ERROR: expecting keyword MAX

DESCRIPTION

The keyword MAX is expected to indicate the maximum value for the data type of the associated field in the *DM_ROUTING section of the DMCONFIG file.

ACTION

Check the range and the remote domain name specified in the *DM_ROUTING section of the DMCONFIG file. The keyword MAX should be specified to indicate the maximum value for the data type of the associated field.

SEE ALSO

DMCONFIG (5)

4063 ERROR: expecting keyword MIN

DESCRIPTION

The keyword MIN is expected to indicate the minimum value for the data type of the associated field in the *DM_ROUTING section of the DMCONFIG file.

ACTION

Check the range and the remote domain name specified in the *DM_ROUTING section of the DMCONFIG file. The keyword MIN should be specified to indicate the minimum value for the data type of the associated field.

SEE ALSO

DMCONFIG (5)

4064 ERROR: expecting keyword MIN or MAX

DESCRIPTION

The keyword MAX or MIN is expected to indicate the maximum or minimum value for the data type of the associated field in the *DM_ROUTING section of the DMCONFIG file.

ACTION

Check the range and the remote domain name specified in the *DM_ROUTING section of the DMCONFIG file. The keyword MAX or MIN should be specified to indicate the maximum or minimum value for the data type of the associated field.

SEE ALSO

DMCONFIG (5)

4065 ERROR: cannot have a '-' in front of MAX or MIN

DESCRIPTION

The routing range cannot have a '-' sign in front of the MAX or MIN value.

ACTION

Check the routing data in the *DM_ROUTING section of the DMCONFIG file. Remove any '-' sign in front of the MAX or MIN value.

SEE ALSO

DMCONFIG (5)

4066 ERROR: value out of range for a short value

DESCRIPTION

The routing value for a short routing data is out of range.

ACTION

Check routing range values for the short routing data in the *DM_ROUTING section of the DMCONFIG file.

SEE ALSO

DMCONFIG (5)

4067 ERROR: value out of range for an int value

DESCRIPTION

The routing value for an integer routing data is out of range.

ACTION

Check routing range values for the integer routing data in the *DM_ROUTING section of the DMCONFIG file.

SEE ALSO

DMCONFIG (5)

4068 ERROR: value out of range for a long value

DESCRIPTION

The routing value for a long routing data is out of range.

ACTION

Check routing range values for the long routing data in the *DM_ROUTING section of the DMCONFIG file.

SEE ALSO

DMCONFIG (5)

4069 ERROR: cannot have a '-' and a '+' sign in front of a number

DESCRIPTION

The routing range cannot have a '-' and '+' sign in front of a number.

ACTION

Check the routing range data in the *DM_ROUTING section of the DMCONFIG file. If a '-' and a '+' sign are both in front of a number, remove the '+' sign.

SEE ALSO

DMCONFIG (5)

4070 ERROR: cannot have a '-' in front of MAX or MIN

DESCRIPTION

While loading all of the information that is in the BDMCONFIG file into the shared memory, the calling process failed to get a data routing entry. The failure occurred while parsing a range string into data based on the field type information of one of the entries in the *DM_ROUTING section of the configuration file. The calling process was unable to create the data routing entry.

ACTION

Make sure the RANGES parameter in the *DM_ROUTING section of the DMCONFIG file is valid. The range strings may not contain a '-' in front of MIN or MAX.

SEE ALSO

DMCONFIG (5)

4071 ERROR: expecting a ' ', '+', '-' or number after 'e/E' in float/double

DESCRIPTION

A '', '+', '-' or number after 'e' or 'E' is expected for float or double routing values.

ACTION

Check the routing range values of the float and double in the *DM_ROUTING section of the DMCONFIG file.

SEE ALSO

DMCONFIG (5)

4072 ERROR: value out of range for a float value

DESCRIPTION

The routing value for a float routing data is out of range.

ACTION

Check routing range values for the float routing data in the *DM_ROUTING section of the DMCONFIG file.

SEE ALSO

DMCONFIG (5)

4073 ERROR: value out of range for a double value

DESCRIPTION

The routing value for a double routing data is out of range.

ACTION

Check routing range values for the double routing data in the *DM_ROUTING section of the DMCONFIG file.

SEE ALSO

DMCONFIG (5)

4074 ERROR: cannot have a '-' in front of MAX or MIN

DESCRIPTION

The routing range cannot have a '-' and '+' sign in front of the MAX or MIN value.

ACTION

Check the routing range data in the *DM_ROUTING section of the DMCONFIG file. Remove any '-' sign in front of the MAX or MIN value.

SEE ALSO

DMCONFIG (5)

4075 ERROR: expected single quote to begin char routing data value

DESCRIPTION

A single quote (') is expected at the beginning of char routing data.

ACTION

Check routing range values for the char routing data in the *DM_ROUTING section of the DMCONFIG file. A char routing data must begin with a single quote (').

SEE ALSO

DMCONFIG (5)

4076 ERROR: expected single quote to end char routing data value

DESCRIPTION

A single quote (') is expected at the end of char routing data.

ACTION

Check routing range values for the char routing data in the *DM_ROUTING section of the DMCONFIG file. A char routing data must be ended with a single quote (').

SEE ALSO

DMCONFIG (5)

4077 ERROR: cannot have a '-' in front of MAX or MIN

DESCRIPTION

The routing range cannot have a '-' and '+' sign in front of the MAX or MIN value.

ACTION

Check the routing range data in the *DM_ROUTING section of the DMCONFIG file. Remove any '-' sign in front of the MAX or MIN value.

SEE ALSO

DMCONFIG (5)

4078 ERROR: expected single quote for string/carray routing data value

DESCRIPTION

A single quote (') is expected for string and carray routing data.

ACTION

Check routing range values for the string and carray routing data in the *DM_ROUTING section of the DMCONFIG file. The string and carray routing data must be within single quotes (').

SEE ALSO

DMCONFIG (5)

4079 ERROR: not enough string pool space available for routing info

DESCRIPTION

There is not enough routing free string pool space in the shared memory when filling the data section with string and carray data.

ACTION

This is s system error, contact your TUXEDO System Technical Support.

SEE ALSO

DMCONFIG (5)

4080 ERROR: cannot have a '-' and a '+' sign in front of a number

DESCRIPTION

The routing range cannot have a '-' and '+' sign in front of a number.

ACTION

Check the routing range data in the *DM_ROUTING section of the DMCONFIG file. If a '-' and a '+' sign are both in front of a number, remove the '+' sign.

SEE ALSO

DMCONFIG (5)

4081 ERROR: cannot have a '-' in front of MAX or MIN

DESCRIPTION

The routing range cannot have a '-' and '+' sign in front of the MAX or MIN value.

ACTION

Check the routing range data in the *DM_ROUTING section of the DMCONFIG file. Remove any '-' sign in front of the MAX or MIN value.

SEE ALSO

DMCONFIG (5)

4082 ERROR: invalid format for decimal

DESCRIPTION

The routing range packed decimal data are specified incorrectly.

ACTION

Check routing range packed decimal data in the *DM_ROUTING section of the DMCONFIG file. The decimal data must be in the correct format.

SEE ALSO

DMCONFIG (5)

4083 ERROR: discovered NULL character in string routing data value

DESCRIPTION

A NULL character is found in the string routing data.

ACTION

Check the string routing data for NULL characters in the *DM_ROUTING section of the DMCONFIG file. A string value is terminated with a NULL character.

SEE ALSO

DMCONFIG (5)

4084 ERROR: Routing field for 'routing_field' null

DESCRIPTION

During data-dependent routing for an FML buffer, the specified 'routing_field' value in the FML buffer was null.

ACTION

Make sure the routing field is correctly set in the FML buffer.

SEE ALSO

DMCONFIG (5)

4085 ERROR: Field type of buffer does not match routing criteria type

DESCRIPTION

During data-dependent routing of an FML typed buffer, the field type for the routing field didn't match the field type for the typed buffers. This should not occur during normal system operation.

ACTION

Contact your TUXEDO System Technical Support.

SEE ALSO

DMCONFIG (5)

4086 ERROR: Illegal offset value for routing_field

DESCRIPTION

Data-dependent routing failed for a VIEW buffer because the offset for the routing field is invalid. This should not occur during normal system operation.

ACTION

Contact your TUXEDO System Technical Support.

SEE ALSO

DMCONFIG (5)

4087 ERROR: Routing field for 'routing_field' null

DESCRIPTION

During data-dependent routing for a VIEW buffer, the specified 'routing_field' value in the VIEW buffer was null.

ACTION

Make sure the routing field is correctly set in the VIEW buffer.

SEE ALSO

DMCONFIG (5)

4089 ERROR: _dmcf_OLD_open failed: Can't open DM_PASSWORDS section

DESCRIPTION

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM couldn't open the BDMCONFIG file for reading the *DM_PASSWORDS section.

ACTION

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

SEE ALSO

DMCONFIG (5)

4090 ERROR: _dmcf_OLD_open failed: Can't open DM_PASSWORDS section

DESCRIPTION

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM couldn't open the BDMCONFIG file for reading the *DM_PASSWORDS section.

ACTION

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

SEE ALSO

DMCONFIG (5)

4091 ERROR: Can't add PASSWORD entry into table

DESCRIPTION

When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it couldn't load a PASSWORD into shared memory. This should only occur if the GWADM administrative server couldn't find free space in the existing shared memory segments and it couldn't create additional shared memory segments to add the new entry.

ACTION

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

SEE ALSO

DMCONFIG (5)

4092 ERROR: _dmcf_OLD_open failed: Can't open DM_RESOURCES section

DESCRIPTION

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM couldn't open the BDMCONFIG file for reading the *DM_RESOURCES section.

ACTION

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

SEE ALSO

DMCONFIG (5)

4093 ERROR: Can't add RESOURCES entry into table

DESCRIPTION

When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it couldn't load the *DM_RESOURCES info into shared memory. This should only occur if the shared memory is corrupted.

ACTION

Contact your TUXEDO System Technical Support.

SEE ALSO

DMCONFIG (5)

LIBGW MESSAGES 4100-4199

4101 ERROR: _dmcf_OLD_open failed: Can't open DM_RDOMSECS section

DESCRIPTION

The Domain Administrative server detected an internal error. The *DM_RDOMSECS section of the bdmconfig file could not be opened.

ACTION

This is an internal error with no associated user action. If the message persists, contact your TUXEDO System Technical Support with the exact error message.

SEE ALSO

DMADMIN (1)

4102 ERROR: _dmcf_OLD_open failed: Can't open DM_RDOMUSR section

DESCRIPTION

The Domain Administrative server detected an internal error. The *DM_RDOMUSR section of the bdmconfig file could not be opened.

ACTION

This is an internal error with no associated user action. If the message persists, contact your TUXEDO System Technical Support with the exact error message.

SEE ALSO

DMADMIN (1)

LIBGW MESSAGES 5000-5099

5000 ERROR: Can't get offset for view viewname

DESCRIPTION

Cannot get offset for view, viewname, in routing entry. Possible causes: 1) the view, viewname, is not defined in your environment variable VIEWFILES, 2) it doesn't exist, or 3) the FIELD specified in the routing section is not defined in the view, viewname.

ACTION

Check your environment variables VIEWFILES and VIEWDIR to see if the view, viewname, is defined. Also, check to see if the view file exists under the VIEWDIR. Then, check the FIELD defined in the *DM_ROUTING section of the DMCONFIG file to see if they are indeed defined in the view files.

SEE ALSO

DMCONFIG (5)

5001 ERROR: Can't put FIELDTBLS into environment

DESCRIPTION

The TUXEDO administrative server was unable to reset FIELDTBLS in the process's environment using putenv().

ACTION

Make the existing environment smaller by unsetting some unneeded variables (or make environment larger if the operating system allows it) and re-execute the program.

SEE ALSO

DMCONFIG (5)

5002 ERROR: Environment variable TUXDIR not defined

DESCRIPTION

The TUXEDO administrative server didn't have TUXDIR set in its environment.

ACTION

SEE ALSO

DMCONFIG (5)

5003 ERROR: Can't put FIELDTBLDIR into environment

DESCRIPTION

The TUXEDO administrative server was unable to reset FLDTBLDIR in the process's environment using putenv().

ACTION

Make the existing environment smaller by unsetting some unneeded variables (or make environment larger if the operating system allows it) and re-execute the program.

SEE ALSO

DMCONFIG (5)

5004 ERROR: Fldid failed(Ferror=err). Can't find TA_SRVGRP in FIELDTBLS files

DESCRIPTION

The TUXEDO administrative server couldn't find the definition for one of the system fields.

ACTION

Contact your TUXEDO System Technical Support.

SEE ALSO

DMCONFIG (5)

5005 WARN: pid=pid died leaving SHM locked; cleaning up

DESCRIPTION

A process that was attached to the BB died and holds a user-level semaphore, so the BB is cleaning up.

ACTION

No action required for BB, but you may want to investigate why the process died.

5006 WARN: Ticket stuck high - retrying

DESCRIPTION

While monitoring the integrity of the Bulletin Board, the BBL found a TUXEDO System user-level semaphore with no owner. In addition, another process was waiting to be served. The BBL must therefore become the owner of the semaphore and delegate it to the waiting process. While trying to do so, the BBL failed to lock the Bulletin Board, and will attempt to lock it again.

ACTION

No action required.

5007 WARN: Ticket stuck high - retrying

DESCRIPTION

While monitoring the integrity of the Bulletin Board, the BBL found a TUXEDO System user-level semaphore with no owner. In addition, another process was waiting to be served. The BBL must therefore become the owner of the semaphore and delegate it to the waiting process. While trying to do so, the BBL failed to lock the Bulletin Board, and will attempt to lock it again.

ACTION

No action required.

5008 WARN: Ticket stuck high - resetting

DESCRIPTION

While monitoring the integrity of the Bulletin Board, the BBL found a TUXEDO System user-level semaphore with no owner. In addition, another process was waiting to be served. The BBL must therefore become the owner of the semaphore and delegate it to the waiting process. The BBL managed to lock the Bulletin Board, transfer the ownership of the semaphore, and adjust the statistics.

ACTION

No action required.

5009 WARN: warning: SHM owned by pid, but not locked

DESCRIPTION

Either the machine does not have proper atomic increment for the user-level semaphore, or there are too many signals coming to the process too quickly.

ACTION

Contact your TUXEDO System Technical Support.

5010 WARN: SHM lock appears stuck: held by pid=pid

DESCRIPTION

The process has held the lock on the BB for a longer than normal period of time. The process could still be alive, but incorrectly holding the user-level semaphore.

ACTION

Check the status of the process that is holding the lock. It might be hung, or it is holding the lock for too long a period of time while doing work.

5012 ERROR: Attempted to add a duplicate record with key=key in section section

DESCRIPTION

An attempt to add an entry to a table in shared memory failed because it violated the primary key constraint.

ACTION

Re-submit the operation with a valid key value for the record.

SEE ALSO

DMCONFIG (5)

5013 ERROR: Can't delete file file in APPDIR used for storing OSITP blob

DESCRIPTION

The GWOSITP process was unable to delete a file it created earlier for storing OSITP BLOB.

ACTION

Check to make sure that the file still exists. If the file doesn't exist, refrain from deleting files used for saving BLOBS.

SEE ALSO

DMCONFIG (5)

5016 ERROR: Can't open file file in APPDIR for reading OSITP blob

DESCRIPTION

The GWOSITP process was unable to open a file for reading in the APPDIR directory that it created earlier.

ACTION

Check to make sure that the file still exists. If the file doesn't exist, refrain from deleting files used for saving BLOBS.

SEE ALSO

DMCONFIG (5)

5017 ERROR: Can't read OSITP blob from file file in APPDIR

DESCRIPTION

The GWOSITP process was unable to read a file in the APPDIR directory that it created earlier.

ACTION

Check to make sure that the file still exists. If the file doesn't exist, refrain from deleting files used for saving BLOBS.

SEE ALSO

DMCONFIG (5)

5018 ERROR: Can't get password entry for RDOM=domain from shmem

DESCRIPTION

When a gateway process establishes a connection with a remote domain, the connecting domain has to pass the security check of the remote domain. If the remote domain is enforcing DM_PW security, then the initiator must have a *DM_PASSWORD entry in the BDMCONFIG file corresponding to the remote domain. This message indicates that the password for the remote domain is not available.

ACTION

Execute the dmadmin program and add a *DM_PASSWORD entry for the remote domain, and then re-establish connection with the remote domain.

SEE ALSO

DMCONFIG (5)

5019 ERROR: Can't create more than num segments for a domain

DESCRIPTION

The GWADM server's attempt to create a shared memory segment failed. There is a fixed upper bound for the number of shared memory segments that can be created by a local domain. If this limit is reached, it means that there have been lots of dynamic insertions for this local domain.

ACTION

By shutting down the application and rebooting it, you can coalesce the shared memory segments.

5020 ERROR: Memory allocation failure

DESCRIPTION

An attempt dynamically to allocate memory from the operating system using malloc() failed while attempting to log a transaction. For the most common types of log records, this will result in the transaction being aborted.

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.

5023 ERROR: Cannot get fieldid for fld

DESCRIPTION

A system error occurred in getting the field identifier when loading the routing entry into the Bulletin Board.

ACTION

Check the field tables to see if the field specified in the routing table is defined. Also, check your environment variables FLDTBLDIR and FIELDTBLS.

SEE ALSO

DMCONFIG (5)

5024 ERROR: dmroute failed, could not find routing criteria of routing_name for buffer type FML32

DESCRIPTION

A routing_name was specified for a *DM_REMOTE_SERVICES entry in the DMCONFIG file that does not appear in the *DM_ROUTING section, and the standard FML32 routing function is used (which requires a matching *DM_ROUTING entry).

ACTION

Correct and re-load the DMCONFIG file, or provide an application-specific routing function for FML32 typed buffers.

SEE ALSO

DMCONFIG (5)

5025 ERROR: dmroute failed, could not find routing criteria of routing_name for buffer type FML32

DESCRIPTION

A routing_name was specified for a *DM_REMOTE_SERVICES entry in the DMCONFIG file that does not appear in the *DM_ROUTING section, and the standard FML32 routing function is used (which requires a matching *DM_ROUTING entry).

ACTION

Correct and re-load the DMCONFIG file, or provide an application-specific routing function for FML32 typed buffers.

SEE ALSO

DMCONFIG (5)

5026 ERROR: Routing field for 'routing_field' null

DESCRIPTION

During data-dependent routing for an FML32 buffer, the specified 'routing_field' value in the FML32 buffer was null.

ACTION

Make sure the routing field is correctly set in the FML32 buffer.

SEE ALSO

DMCONFIG (5)

5027 ERROR: Field type of buffer does not match routing criteria type

DESCRIPTION

During data-dependent routing of an FML32 typed buffer, the field type for the routing field didn't match the field type for the typed buffers. This should not occur during normal system operation.

ACTION

Contact your TUXEDO System Technical Support.

SEE ALSO

DMCONFIG (5)

5028 ERROR: unknown field type used for FML32 routing

DESCRIPTION

During data-dependent routing of an FML32 typed buffer, an unknown field type was encountered for the routing field. This should not occur during normal system operation.

ACTION

Contact your TUXEDO System Technical Support.

SEE ALSO

DMCONFIG (5)

5029 ERROR: Routing field value for 'service' not valid

DESCRIPTION

While doing data-dependent routing on an FML32 typed buffer for the specified service service, the routing field value did not match any of the ranges specified in the routing criteria and the criteria did not contain a wild-card pattern.

ACTION

Make sure the routing field value is valid. Correct the routing criteria in the RANGES value of the DMCONFIG file.

SEE ALSO

DMCONFIG (5)

5030 ERROR: Can't add REMOTE SECURITY MAP (RDOMSEC) entry into table

DESCRIPTION

The Gateway Administrative server detected an internal error during initialization. An internal function call returned a failure trying to add an entry to the RDOMSEC table in shared memory.

ACTION

This is an internal error with no associated user action. If the message persists, contact your TUXEDO System Technical Support with the exact error message.

SEE ALSO

GWADM (5)

5031 ERROR: Can't add REMOTE USER (RDOMUSR) entry into table

DESCRIPTION

The Gateway Administrative server detected an internal error during initialization. An internal function call returned a failure trying to add an entry to the RDOMUSR table in shared memory.

ACTION

This is an internal error with no associated user action. If the message persists, contact your TUXEDO System Technical Support with the exact error message.

SEE ALSO

GWADM (5)

5035 ERROR: Can't add RSEC entry into table

DESCRIPTION

The Gateway Administrative server detected an internal error. An internal function call returned a failure trying to add an entry to the RSEC table in shared memory.

ACTION

This is an internal error with no associated user action. If the message persists, contact your TUXEDO System Technical Support with the exact error message.

SEE ALSO

GWADM (5)

5036 ERROR: Can't add RSEC entry into table

DESCRIPTION

The Gateway Administrative server detected an internal error. An internal function call returned a failure trying to add an entry to the RSEC table in shared memory.

ACTION

This is an internal error with no associated user action. If the message persists, contact your TUXEDO System Technical Support with the exact error message.

SEE ALSO

GWADM (5)

5037 ERROR: Can't add PRINAPPKEY entry into table

DESCRIPTION

The Gateway Administrative server detected an internal error. An internal function call returned a failure trying to add an entry to the PRINAPPKEY table in shared memory.

ACTION

This is an internal error with no associated user action. If the message persists, contact your TUXEDO System Technical Support with the exact error message.

SEE ALSO

GWADM (5)

5038 ERROR: Can't setup links from RSEC table to RDOMSEC entries

DESCRIPTION

The Domain Gateway library software detected an error while trying to initialize the Gateway Administrative server. The process was unable to set up the links to the shared memory table for the remote domain.

ACTION

This is an internal error with no associated user action. If the error persists, contact your Tuxedo System technical support with the exact error message.

SEE ALSO

GWADM (5)

5039 ERROR: Can't setup principal-appkey mappings

DESCRIPTION

The Domain Gateway library software detected an error while trying to initialize the Gateway Administrative server. The process was unable to set up the principal-appkey mappings.

ACTION

This is an internal error with no associated user action. If the error persists, contact your Tuxedo System technical support with the exact error message.

SEE ALSO

GWADM (5)

5040 ERROR: Can't setup links from RSEC table to RDOMUSR entries

DESCRIPTION

The Domain Gateway library software detected an error while trying to initialize the Gateway Administrative server. The process was unable to set up the links to the shared memory table for the remote domain.

ACTION

This is an internal error with no associated user action. If the error persists, contact your Tuxedo System technical support with the exact error message.

SEE ALSO

GWADM (5)

5041 ERROR: Can't get VIEW32 offset for view type

DESCRIPTION

The Domain Gateway library software detected an error while trying to initialize the Gateway Administrative server. An internal function call returned an error. The process was unable to get the offset for type.

ACTION

This is an internal error with no associated user action. If the error persists, contact your Tuxedo System technical support with the exact error message.

SEE ALSO

GWADM (5)

LIBGW MESSAGES 5200-5299

5200 WARN: Transaction became HEURISTIC HAZARD

DESCRIPTION

The Domain Gateway library software detected this condition while trying to process a commit operation. This messages indicates that the transaction is in a HEURISTIC HAZARD state. This is a warning message to alert the user that the transaction may be out of synchronization.

ACTION

Review the transaction log for the transaction and attempt to determine the cause for the indicated condition.

SEE ALSO

tpcommit (3)

5201 WARN: Transaction became HEURISTIC MIX

DESCRIPTION

The Domain Gateway library software detected this condition while trying to process a commit operation. This messages indicates that the transaction is in a HEURISTIC MIX state. This is a warning message to alert the user that the transaction may be out of synchronization.

ACTION

Review the transaction log for the transaction and attempt to determine the cause for the indicated condition.

SEE ALSO

tpcommit (3)

5202 WARN: Transaction returning HEURISTIC HAZARD result

DESCRIPTION

The Domain Gateway library software detected this condition while trying to process a TMS_DONE event. This messages indicates that the transaction is in a HEURISTIC HAZARD state. This is a warning message to alert the user that the transaction may be out of synchronization.

ACTION

Review the transaction log for the transaction and attempt to determine the cause for the indicated condition.

SEE ALSO

tpcommit (3)

5203 WARN: Transaction returning HEURISTIC MIX result

DESCRIPTION

The Domain Gateway library software detected this condition while trying to process a TMS_DONE event. This messages indicates that the transaction is in a HEURISTIC MIX state. This is a warning message to alert the user that the transaction may be out of synchronization.

ACTION

Review the transaction log for the transaction and attempt to determine the cause for the indicated condition.

SEE ALSO

tpcommit (3)

5204 ERROR: Invalid action action specified

DESCRIPTION

The Domain Gateway library software detected an internal error while trying to schedule an action to be processed. The action specified is not a valid action.

ACTION

This is an internal error with no associated user action. If the error persists, contact your Tuxedo System technical support with the exact error message.

SEE ALSO

tpstrerror (3)

5205 ERROR: Maximum action table size(max size) reached

DESCRIPTION

The Domain Gateway library software detected an internal error while trying to schedule an action to be processed. The action table has reached the maximum size allowable max size.

ACTION

This is an internal error with no associated user action. If the error persists, contact your Tuxedo System technical support with the exact error message.

SEE ALSO

tpstrerror (3)

5206 ERROR: No more memory available to expand action table

DESCRIPTION

The Domain Gateway library software detected an internal error while trying to schedule an action to be processed. The action table cannot be expanded due to the lack of virtual memory.

ACTION

Attempt to identify and stop any extraneous processes to free up virtual memory on your system.

SEE ALSO

tpstrerror (3)

5207 ERROR: Program limit exceeded, terminate Domain Gateway process

DESCRIPTION

The Domain Gateway library software detected an internal error while trying to schedule an action to be processed. The action table has reached the maximum size allowable and the maximum number of failures of this type has been reached.

ACTION

Shutdown the failed Domain Gateway process and then restart it to clear the error condition.

SEE ALSO

tpstrerror (3)

5208 ERROR: Unable to recover, terminate Domain Gateway process

DESCRIPTION

The Domain Gateway library software detected an internal error while trying to schedule an action to be processed. The maximum number of scheduling failures has been reached and the process cannot recover.

ACTION

Shutdown the failed Domain Gateway process and then restart it to clear the error condition.

SEE ALSO

tpstrerror (3)

5209 ERROR: _dmcf_OLD_open failed: Can't open DM_SNADOM section

DESCRIPTION

The Domain Administrative server detected an internal error during initialization. The *DM_SNADOM section of the bdmconfig file could not be opened.

ACTION

This is an internal error with no associated user action. If the message persists, contact your TUXEDO System Technical Support with the exact error message.

SEE ALSO

DMADMIN (1)

5210 ERROR: _dmcf_OLD_open failed: Can't open DM_RDOMSEC section

DESCRIPTION

The Domain Administrative server detected an internal error during initialization. The *DM_RDOMSEC section of the bdmconfig file could not be opened.

ACTION

This is an internal error with no associated user action. If the message persists, contact your TUXEDO System Technical Support with the exact error message.

SEE ALSO

DMADMIN (1)

5211 ERROR: _dmcf_OLD_open failed: Can't open DM_RDOMUSR section

DESCRIPTION

The Domain Administrative server detected an internal error during initialization. The *DM_RDOMUSR section of the bdmconfig file could not be opened.

ACTION

This is an internal error with no associated user action. If the message persists, contact your TUXEDO System Technical Support with the exact error message.

SEE ALSO

DMADMIN (1)

5212 ERROR: Can't add SNADOM entry into table

DESCRIPTION

The Gateway Administrative server detected an internal error during initialization. An internal function call returned a failure trying to add an entry to the SNADOM table in shared memory.

ACTION

This is an internal error with no associated user action. If the message persists, contact your TUXEDO System Technical Support with the exact error message.

SEE ALSO

GWADM (5)

5213 ERROR: _dmcf_OLD_open failed: Can't open DM_SNADOM section

DESCRIPTION

The Domain Administrative server detected an internal error during initialization. The *DM_SNADOM section of the bdmconfig file could not be opened.

ACTION

This is an internal error with no associated user action. If the message persists, contact your TUXEDO System Technical Support with the exact error message.

SEE ALSO

DMADMIN (1)

5214 ERROR: Unable to determine license level

DESCRIPTION

An error occured while retrieving the current license attributes.

ACTION

Check the log for prior messages indicating the cause of the problem. Normally, it means that the product has not been licensed properly.

5215 WARN: Domain compression configured for val, but no license available

DESCRIPTION

You do not have a license to use Domains compression.

ACTION

Purchase a license for Domains compression.

5216 ERROR: Unable to determine license level

DESCRIPTION

An error occured while retrieving the current license attributes.

ACTION

Check the log for prior messages indicating the cause of the problem. Normally, it means that the product has not been licensed properly.

5217 ERROR: Domain compression configured for val, but no license available

DESCRIPTION

You do not have a license to use Domains compression.

ACTION

Purchase a license for Domains compression.

5218 ERROR: Unable to determine license level

DESCRIPTION

An error occured while retrieving the current license attributes.

ACTION

Check the log for prior messages indicating the cause of the problem. Normally, it means that the product has not been licensed properly.

5219 ERROR: Domain compression configured for val, but no license available

DESCRIPTION

You do not have a license to use Domains compression.

ACTION

Purchase a license for Domains compression.

5220 WARN: Domain svc advertising can only be done with dmadmin

DESCRIPTION

You attempted to dynamically advertise a domain service via tmadmin. This is only allowed via dmadmin.

ACTION

Use dmadmin to advertise the remote domain service.

SEE ALSO

dmadmin (1)

5221 ERROR: Can't add name entry into table table. (IC = code)

DESCRIPTION

An error was encountered by the Gateway Administrative Server (GWADM) while building shared memory tables during server initialization. Entry name could not be added to the shared memory table table. The value of code is an internal error code used for diagnosis.

ACTION

This is an internal error with no associated user action. If the error persists, contact your TUXEDO System Technical Support with the exact error message. SEE ALSO

GWADM (5)

5222 ERROR: _dmcf_OLD_open failed: Can't open section section. (IC = code)

DESCRIPTION

An error was encountered by the Domain Administrative Server (DMADM) while attempting to open the BDMCONFIG file. The section section could not be opened. The sections of the bdmconfig may be unreadable due to corruption of the bdmconfig file. The value of code is an internal error code used for diagnosis.

ACTION

Attempt to unload the bdmconfig file using dmunloadcf(1). If the bdmconfig file is corrupted, it may be necessary to rebuild the bdmconfig file from the ascii version DMCONFIG file using dmloadcf(1). SEE ALSO

DMADM (5)

dmunloadcf (1)

dmloadcf (1)

5223 ERROR: Can't setup links from name entry to name entry. (IC = code)

DESCRIPTION

An error was encountered by the Gateway Administrative Server (GWADM) while linking shared memory tables during server initialization. The named entries could not be linked in shared memory. The value of code is an internal error code used for diagnosis.

ACTION

This is an internal error with no associated user action. If the error persists, contact your TUXEDO System Technical Support with the exact error message. SEE ALSO

GWADM (5)

5224 ERROR: Bad conversational sequence number

DESCRIPTION

The /Domain gateway encountered a problem while processing a conversational message. The conversational message was received in the incorrect order.

ACTION

This is an internal processing error with no associated user action. If the problem persists, contact your BEA TUXEDO System Technical Support.

SEE ALSO

DMCONFIG(5)

5225 ERROR: Recovery cannot insert log record blob

DESCRIPTION

The Domain Gateway detected an error during warmstart processing. The Domain Gateway was unable to restore the Network transaction blob in shared memory during transaction recovery. This can occur because either an internal pointer was corrupted, the shared memory lock could not be obtained, or storage could not be obtained.

ACTION

This is an internal processing error with no associated user action. If the problem persists, contact your BEA TUXEDO System Technical Support.

5226 ERROR: Memory allocation failure, size(bytes)

DESCRIPTION

A domain gateway process detected an error during initialization processing. The gateway process was unable to allocate memory for the gateway information data structure.

ACTION

Shut down unused applications, and reboot the Gateway.

5227 ERROR: Cannot get Local Domain from shared memory

DESCRIPTION

A domain gateway process detected an error during initialization processing. The gateway process was unable to retrieve local domain definition information from shared memory. This can occur if there is another process holding the shared memory lock, or if the record is missing from shared memory.

ACTION

Ensure that the Local Domain definition in the dmconfig(5) file is correct. If the problem persists, contact your BEA TUXEDO System Technical Support.

SEE ALSO

dmconfig(5)

5228 ERROR: Cannot get Local Domain ID from shared memory

DESCRIPTION

The Domain Gateway Server encountered an error during initialization processing. The Gateway process was unable to obtain the Domain Gateway shared memory lock.

ACTION

This is an internal error with no associated user action. If the problem persists, contact your BEA TUXEDO System Technical Support.

5229 ERROR: Can't release domain shared memory lock

DESCRIPTION

The Gateway Administrative Server (GWADM) encountered an error while checking for transaction log requests. The GWADM process was unable to release the /Domain Gateway shared memory lock.

ACTION

This is an internal processing error with no associated user action. If the problem persists, contact your Tuxedo System Technical Support. SEE ALSO

GWADM(5)

5230 ERROR: Cannot get shmem lock, failed to clear the old events

DESCRIPTION

The Domain Gateway Server encountered an error during initialization processing. The Gateway process was unable to obtain the Domain Gateway shared memory lock.

ACTION

This is an internal error with no associated user action. If the problem persists, contact your Tuxedo System Technical Support.

5231 ERROR: Can't get domain shared memory lock

DESCRIPTION

The Gateway Administrative Server (GWADM) encountered an error while checking for transaction log requests. The GWADM process was unable to obtain the /Domain Gateway shared memory lock.

ACTION

This is an internal processing error with no associated user action. If the problem persists, contact your Tuxedo System Technical Support.

5232 ERROR: Cannot access Domain log table

DESCRIPTION

The Domain Gateway process encountered an error during initialization processing. The Gateway process was unable to access the Domain Gateway transaction log table in shared memory.

ACTION

This is an internal processing error with no associated user action. If the problem persists, contact your Tuxedo System Technical Support.

5231 ERROR: Can't get domain shared memory lock

DESCRIPTION

The Gateway Administrative Server (GWADM) encountered an error while checking for transaction log requests. The GWADM process was unable to obtain the /Domain Gateway shared memory lock.

ACTION

This is an internal processing error with no associated user action. If the problem persists, contact your BEA TUXEDO System Technical Support.

5232 ERROR: Cannot access Domain log table

DESCRIPTION

The Domain Gateway process encountered an error during initialization processing. The Gateway process was unable to access the Domain Gateway transaction log table in shared memory.

ACTION

This is an internal processing error with no associated user action. If the problem persists, contact your BEA TUXEDO System Technical Support.

5233 ERROR: Recovery cannot set branch state for domain domain name

DESCRIPTION

The Domain Gateway process encountered an error during warmstart processing. The Gateway process for domain failed to set a transaction branch to a known state during transaction recovery. This can be caused by failing to get the shared memory lock, by reaching the maximum number of remote domains that can be involved in one transaction, or by reaching the maximum number of transactions allowed for this Domain Gateway.

ACTION

Make sure that the MAXTRAN, and the MAXRDTRAN parameters in the dmconfig(5) file are set appropriately for your application. If the problem persists, contact your BEA TUXEDO System Technical Support.

SEE ALSO

dmconfig(5) file are set appropriately for

5234 INFO: Warmstart processing transaction as coordinating domain

DESCRIPTION

This is an informational message indicating that the Domain Gateway process is the transaction coordinator during warmstart processing. The Domain Gateway is recovering transactions from the Domain transaction log. For the transaction identified as part of the userlog(3) message, the Domain Gateway is the coordinator of the transaction.

ACTION

No action needed, this is an informational message.

SEE ALSO

userlog(3)

5235 INFO: Warmstart processing transaction as subordinate to domain domain name

DESCRIPTION

This is an informational message indicating that the Domain Gateway process is subordinate to domain <domain name> during warmstart processing. The Domain Gateway is recovering transctions from the Domain transaction log. For the transaction identified as part of the userlog(3) message, the Domain Gateway is subordinate to coordinator domain <domain name>.

ACTION

No action needed, this is an informational message.

SEE ALSO

userlog(3)

5236 ERROR: Can't get domain shared memory lock!

DESCRIPTION

The Gateway Administrative Server (GWADM) encountered an error while writing a transaction log record. The Gateway process was unable to obtain the shared memory lock.

ACTION

This is an internal processing error with no associated user action. If the problem persists, contact your BEA TUXEDO System Technical Support.

SEE ALSO

GWADM(5)

5237 ERROR: Can't release domain shared memory lock!

DESCRIPTION

The Gateway Administrative Server (GWADM) encountered an error while writing a transaction log record. The Gateway process was unable to release the shared memory lock.

ACTION

This is an internal processing error with no associated user action. If the problem persists, contact your BEA TUXEDO System Technical Support.

SEE ALSO

GWADM(5)

5238 ERROR: Can't get domain shared memory lock

DESCRIPTION

The Gateway Administrative Server (GWADM) encountered an error while checking for log requests. The Gateway process was unable to obtain the shared memory lock.

ACTION

This is an internal processing error with no associated user action. If the problem persists, contact your BEA TUXEDO System Technical Support.

SEE ALSO

GWADM(5)

5239 ERROR: Can't release domain shared memory lock

DESCRIPTION

The Gateway Administrative Server (GWADM) encountered an error while checking for log requests. The Gateway process was unable to release the shared memory lock.

ACTION

This is an internal processing error with no associated user action. If the problem persists, contact your BEA TUXEDO System Technical Support.

SEE ALSO

GWADM(5)

5240 INFO: Domain log page page skipped, header chksum didn't match

DESCRIPTION

The Gateway Server encountered a problem during warmstart processing. The Gateway process was unable to process the log page <page> due to a checksum error.

ACTION

This is an informational message with no associated user action.

5241 WARN: Can't send log request to GWADM. Performance may suffer

DESCRIPTION

Can't send log request to GWADM.

ACTION

None. The GWADM will still periodically (every 100ms) check for log requests on the log list. This may result in slower performance, since the log write will not occur until the next time the GWADM checks the log list.

5242 WARN: Can't send log ind to gateway. Performance may suffer

DESCRIPTION

Can't send log indication to gateway.

ACTION

None. The gateway will still periodically (every 100ms) check for log indications on the logged list. This may result in slower performance, since the gateway will not continue processing that transaction until the next time the the gateway checks the logged list.

5243 WARN: Can't send log ind to gateway. Performance may suffer

DESCRIPTION

Can't send log indication to gateway.

ACTION

None. The gateway will still periodically (every 100ms) check for log indications on the logged list. This may result in slower performance, since the gateway will not continue processing that transaction until the next time the the gateway checks the logged list.

5244 ERROR: Invalid sendlist error

DESCRIPTION

The Gateway Server encountered a problem during transaction processing.

ACTION

This is an internal processing error with no associated user action. If the problem persists, contact your Tuxedo System Technical Support.

5245 ERROR: Failed to set non-blocking priority for TMS request

DESCRIPTION

While attempting to send a TMS message, a /Domain gateway process was unable to increase the priority of a non-blocking request. By itself, this failure will not result in any incorrect operation other than a possible minor performance degradation. However, it may be symptomatic of problems elsewhere in the system, since this call should not normally fail.

ACTION

This is an internal processing error with no associated user action. If the problem persists, contact your Tuxedo System Technical Support.

5246 ERROR: Cannot send to service "TMS" due to error "sub"

DESCRIPTION

The /Domain gateway was managing a transaction and had attempted to send a message to a TMS service via a tpacall(), and that call failed. The string value displayed in the message identifies the value of tperrno returned by tpacall().

ACTION

A possible cause for this error may be that the TMS process has terminated for some reason. Please check and ensure that all TMS processes are running. If further assistance is needed, contact the TUXEDO Administrator.

5247 ERROR: Precommit found an invalid transaction state sname

DESCRIPTION

System /T was precommiting a transaction. The transaction state was not one of the states expected.

ACTION

If the problem persists, contact your Tuxedo System Technical Support.

5248 ERROR: Precommit found invalid state group gname state sname

DESCRIPTION

System/T was precommitting a transaction. The transaction state for the indicated group was not as expected.

ACTION

If the problem persists, contact your Tuxedo System Technical Support.