The buffer type information provided in the
configuration file was incorrect.
Check the configuration file,
verify that the buffer type provided is
correct, and repeat the operation.
ubbconfig (5),
tmloadcf (1)
The buffer subtype information provided
in the configuration file was incorrect.
Check the configuration file,
verify that the buffer type provided is
correct, and repeat the operation.
ubbconfig (5),
tmloadcf (1)
The
TUXCONFIG
environment variable is not set.
Set and export the
TUXCONFIG
environment variable, which should be the same as
defined in the
UBBCONFIG
file.
ubbconfig (5)
The
TUXCONFIG
file,
filename,
does not exist.
Check the
TUXCONFIG
environment variable to see if it matches with the definition of the
TUXCONFIG
in the
UBBCONFIG
file. Then, check to see if the
TUXCONFIG
file has been generated. If not, use tmloadcf(1) to create the
TUXCONFIG
file.
tmloadcf (1),
ubbconfig (5)
Cannot get the file status on the
TUXCONFIG
file,
filename.
Check the UNIX errno for reasons and take appropriate actions accordingly.
stats (2)
in UNIX system reference manuals
The
TUXOFFSET
environment variable is less than 0.
Specify a value for the
TUXOFFSET
environment variable that is greater than or equal to 0. This
TUXOFFSET
value must be the same as defined in the
UBBCONFIG
file.
ubbconfig (5)
The
section_name
of the
TUXCONFIG
file cannot be opened. The
TUXCONFIG
file might be corrupted.
You can shut down the application and re-load the
TUXCONFIG file using tmloadcf.
If the error still occurs, contact your TUXEDO System Technical Support.
tmloadcf (1)
Memory allocation failed for adding new sections in the
TUXCONFIG
file.
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.
The
TUXCONFIG
file in the
VTOC
table cannot be closed.
Check the permission and the existence of the
TUXCONFIG
file, or contact your TUXEDO System Technical Support.
Reading an entry from the disk table failed.
Possible causes: 1) the logical table file descriptor was corrupted, 2) the
read page offset was set incorrectly by the system, or 3) the
table itself got corrupted which caused read() to fail.
Check your disk tables such as
VTOC
for possible corruptions and/or
damages. If this error still occurs, contact your TUXEDO System Technical Support.
read (2)
in UNIX system reference manuals
Cannot write to the
section_name
of the
TUXCONFIG
file which was never opened.
Check your
TUXCONFIG
file, or contact your TUXEDO System Technical Support.
tmunloadcf (1),
write(2)
in UNIX system reference manuals
Write to the
section_name
of the
TUXCONFIG
file in VTOC table failed.
Possible causes: 1) the logical table file descriptor was corrupted, 2) the
write page offset was set incorrectly by the system, or 3) the
table itself got corrupted which caused write() to fail.
Check your disk tables such as VTOC for possible corruptions and/or
damages. If this error still occurs, contact your TUXEDO System Technical Support.
write (2)
in UNIX system reference manuals
The routing section of the
TUXCONFIG
file cannot be located.
Possible causes: 1) the
TUXCONFIG
file might be corrupted, 2) the
TUXCONFIG
environment variable might not be set, or 3) the
TUXOFFSET
enironment variable was less than zero.
Contact your TUXEDO System Technical Support.
See Messages 602, 605, and 607 in this chapter
for explanation.
Data routing tables in the Bulletin Board are full when
parsing the routing range and creating the data routing
entries.
This is a system error, contact your TUXEDO System Technical Support.
More than one wild-card (*) range for the short routing data was
specified in the data routing entry.
Check your
UBBCONFIG
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).
ubbconfig (5)
The range values for the short routing data are out of order,
that is, the upper range value is less than the lower range value.
Check routing range values for the short routing data in your
UBBCONFIG
file. The lower range value must be less than or
equal to the upper range value.
ubbconfig (5)
More than one wild-card (*) range for the integer routing data
was specified in the data routing entry.
Check your
UBBCONFIG
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).
ubbconfig (5)
The range values for the integer routing data are out of order,
that is, the upper range value is less than the lower range value.
Check routing range values for the integer routing data in your
UBBCONFIG
file. The lower range value must be less than or
equal to the upper range value.
ubbconfig (5)
More than one wild-card (*) range for the long routing data was
specified in the data routing entry.
Check your
UBBCONFIG
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).
ubbconfig (5)
The range values for the long routing data are out of order,
that is, the upper range value is less than the lower range value.
Check routing range values for the long routing data in your
UBBCONFIG
file. The lower range value must be less than or
equal to the upper range value.
ubbconfig (5)
More than one wild-card (*) range for the float routing data was
specified in the data routing entry.
Check your
UBBCONFIG
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).
ubbconfig (5)
The range values for the float routing data are out of order,
that is, the upper range value is less than the lower range value.
Check routing range values for the float routing data in your
UBBCONFIG
file. The lower range value must be less than or
equal to the upper range value.
ubbconfig (5)
More than one wild-card (*) range for the double routing data was
specified in the data routing entry.
Check your
UBBCONFIG
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).
ubbconfig (5)
The range values for the double routing data are out of order,
that is, the upper range value is less than the lower range value.
Check routing range values for the double routing data in your
UBBCONFIG
file. The lower range value must be less than or
equal to the upper range value.
ubbconfig (5)
More than one wild-card (*) range for the char routing data was
specified in the data routing entry.
Check your
UBBCONFIG
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).
ubbconfig (5)
The range values for the char routing data are out of order,
that is, the upper range value is less than the lower range value.
Check routing range values for the char routing data in your
UBBCONFIG
file. The lower range value must be less than or
equal to the upper range value.
ubbconfig (5)
More than one wild-card (*) range for the string routing data was
specified in the data routing entry.
Check your
UBBCONFIG
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).
ubbconfig (5)
The range values for the string routing data are out of order,
that is, the upper range value is less than the lower range value.
Check routing range values for the string routing data in your
UBBCONFIG
file. The lower range value must be less than or
equal to the upper range value.
ubbconfig (5)
More than one wild-card (*) range for the carray routing data was
specified in the data routing entry.
Check your
UBBCONFIG
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).
ubbconfig (5)
The range values for the carray routing data are out of order,
that is, the upper range value is less than the lower range value.
Check routing range values for the carray routing data in your
UBBCONFIG
file. The lower range value must be less than or
equal to the upper range value.
ubbconfig (5)
An unknown field type was specified in the data routing entry.
Check the field types specified in the ROUTING section of the
UBBCONFIG
file.
ubbconfig (5)
Within a range and a server group pair, the range is separated from
the server group by a colon (:) in the ROUTING section of the
UBBCONFIG
file.
Check the range and server group specified in the ROUTING section of the
UBBCONFIG
file. A colon (:) is expected to separate the range
and the server group.
ubbconfig (5)
Within a range and a server group pair, a comma (,) is expected after
server group name in the ROUTING section of the
UBBCONFIG
file.
600 ERROR: [Invalid buffer type information type]
DESCRIPTION
ACTION
SEE ALSO
601 ERROR: [Invalid buffer subtype information subtype_val]
DESCRIPTION
ACTION
SEE ALSO
602 ERROR: TUXCONFIG environment variable not set
DESCRIPTION
ACTION
SEE ALSO
603 ERROR: TUXCONFIG file filename does not exist
DESCRIPTION
ACTION
SEE ALSO
604 ERROR: Cannot get file status on TUXCONFIG file filename, errno = errno_val
DESCRIPTION
ACTION
SEE ALSO
605 ERROR: TUXOFFSET environment variable must be >= 0
DESCRIPTION
ACTION
SEE ALSO
607 ERROR: Cannot open section section_name of the TUXCONFIG: file
DESCRIPTION
ACTION
SEE ALSO
608 ERROR: Memory allocation failure
DESCRIPTION
ACTION
610 ERROR: Cannot close the TUXCONFIG file
DESCRIPTION
ACTION
612 ERROR: Read an entry from the VTOC table failed
DESCRIPTION
ACTION
SEE ALSO
614 ERROR: Cannot write to the section_name of the TUXCONFIG file which is not opened
DESCRIPTION
ACTION
SEE ALSO
615 ERROR: Write to the section_name of the TUXCONFIG file failed
DESCRIPTION
ACTION
SEE ALSO
616 ERROR: The routing section of the TUXCONFIG file cannot be located
DESCRIPTION
ACTION
624 ERROR: Data tables for routing section full
DESCRIPTION
ACTION
625 ERROR: More than one wild card in entry range
DESCRIPTION
ACTION
SEE ALSO
626 ERROR: Range values out of order upper_range < upper_range
DESCRIPTION
ACTION
SEE ALSO
627 ERROR: More than one wild card in entry range
DESCRIPTION
ACTION
SEE ALSO
628 ERROR: Range values out of order upper_range < lower_range
DESCRIPTION
ACTION
SEE ALSO
629 ERROR: More than one wild card in entry range
DESCRIPTION
ACTION
SEE ALSO
630 ERROR: Range values out of order upper_range < lower_range
DESCRIPTION
ACTION
SEE ALSO
631 ERROR: More than one wild card in entry range
DESCRIPTION
ACTION
SEE ALSO
632 ERROR: Range values out of order upper_range < lower_range
DESCRIPTION
ACTION
SEE ALSO
633 ERROR: More than one wild card in entry range
DESCRIPTION
ACTION
SEE ALSO
634 ERROR: Range values out of order upper_range < lower_range
DESCRIPTION
ACTION
SEE ALSO
635 ERROR: More than one wild card in entry range
DESCRIPTION
ACTION
SEE ALSO
636 ERROR: Range values out of order upper_range < lower_range
DESCRIPTION
ACTION
SEE ALSO
637 ERROR: More than one wild card in entry range
DESCRIPTION
ACTION
SEE ALSO
638 ERROR: Range values out of order for the string routing data
DESCRIPTION
ACTION
SEE ALSO
639 ERROR: More than one wild card in entry range
DESCRIPTION
ACTION
SEE ALSO
640 ERROR: Range values out of order for the carray routing data
DESCRIPTION
ACTION
SEE ALSO
641 ERROR: Unknown field type was specified for data routing entry
DESCRIPTION
ACTION
SEE ALSO
642 ERROR: Expected colon to separate server group range
DESCRIPTION
ACTION
SEE ALSO
643 ERROR: Expected comma after group name grpname,string
DESCRIPTION