An internal TUXEDO System table was requested, and could not be
read because an invalid search key was passed to the low-level
access routine.
Contact your TUXEDO System Technical Support.
One of the internal routines to modify structures in the TUXEDO System/T bulletin board
received a parameter that did not match any of the allowable values.
Contact your TUXEDO System Technical Support.
A
msgctl
kernel call performing an
IPC-STAT
operation failed for message queue
number.
Contact your TUXEDO System Technical Support.
The UNIX System kernel parameters related to message queues
are set too low.
Check the kernel parameters related to message queue capacities,
and increase if necessary.
In particular, check
MSGMNB .
"TUXEDO Installation Guide"
A TUXEDO System process attempted to send a message to another machine,
but the
BRIDGE
system process could not be located.
Shut down and reboot the TUXEDO System on this machine.
An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while
searching for the
BRIDGE
system process's server table entry.
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.
A service could not be advertised because of an invalid internal
handle identifying the server process offering it.
Contact your TUXEDO System Technical Support.
A service could not be advertised because of an internal
data structure inconsistency.
Contact your TUXEDO System Technical Support.
An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while
advertising a service.
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.
One of the internal routines to manage TUXEDO System/T data structures received an
invalid queue table parameter.
This should not occur during normal system operation.
Contact your TUXEDO System Technical Support.
The process just attached to a shared memory region, expecting
to find a TUXEDO System bulletin board.
The header's magic number indicates that it is not a valid bulletin board.
Verify that the configuration file's
IPCKEY
parameter is unique,
and not being used by any other software product on the machine.
The UNIX
ipcs
utility may help diagnose the conflict.
The TUXEDO System software has been updated on the machine,
but this process has not been rebuilt with
the new libraries. It therefore cannot
interpret the bulletin board data structures.
Rebuild the process with updated TUXEDO System libraries.
buildclient (1),
buildserver (1),
buildtms (1),
buildwsh (1),
buildmio (1)
The calling process could not attach to the bulletin board's
shared memory.
It then attempted to create the bulletin board, but
did not have the correct permissions to do so.
Verify that the configuration file's
IPCKEY
parameter is correct,
and that the application is booted.
A server group entry in the bulletin board could
not be created due to an internal error.
Contact your TUXEDO System Technical Support.
A subtype could not be added to the bulletin board
due to an internal error.
Contact your TUXEDO System Technical Support.
The bulletin board's subtype table is full,
and a new subtype cannot be added.
Increase the
MAXBUFSTYPE
parameter in the
configuration file's *RESOURCES section.
A TUXEDO System internal function was used to retrieve service information
from the services table, but a
NULL
service name was used.
Contact your TUXEDO System Technical Support for assistance.
An internal error occurred while a service was
being added to the bulletin board's tables.
Contact your TUXEDO System Technical Support.
An internal data structure inconsistency was detected
while a service was being added to the bulletin board's tables.
Contact your TUXEDO System Technical Support.
The internal routine to create a server table entry received invalid
parameters. This should not happen during normal system operation.
Contact your TUXEDO System Technical Support.
One of the internal routines to manage TUXEDO System/T data structures received an
invalid queue table parameter.
This should not occur during normal system operation.
Contact your TUXEDO System Technical Support.
An attempt to create a server table entry failed because the server was busy.
Wait until the server is no longer busy, and then retry the failed operation.
There are no more queue table entries left in the system.
The number of queue table entries is equal to
the maximum number of servers as specified in the UBBCONFIG file.
Increase the maximum number of servers, as specified by the
MAXSERVERS
parameter in the *RESOURCES section of the UBBCONFIG file.
This can be done by editing the configuration file and reloading
it with
tmloadcf (1),
or it can be done through dynamic administration using the
tmconfig (1)
command.
ubbconfig (5),
tmloadcf (1),
tmconfig (1)
The
BBL
(Bulletin Board Liaison) process is unstable or dead.
Look for associated messages in the userlog related to the
BBL .
These may give more insight about the problem.
If using a multi-node configuration,
make certain that the network is operating properly and
has sufficient bandwidth.
Verify that the TUXEDO System/T administrator or the UNIX System
administrator did not kill the
BBL
process.
Oftentimes, a network that is inoperative or slow may result in a
BBL
response problem.
The internal routine to create an entry in the bulletin board types table
was passed invalid parameters. This should not happen during normal
system operation.
Contact your TUXEDO System Technical Support.
There are no more type table entries left in the system.
An attempt to add an additional type to the bulletin board has failed
due to a lack of space.
The number of type table entries is equal to the number specified
in the UBBCONFIG file.
Increase the maximum number of type table entries, as specified by the
MAXBUFTYPE
parameter in the *RESOURCES section of the UBBCONFIG file.
This can be done by editing the configuration file and reloading it with
tmloadcf (1),
or it can be done through dynamic administration using the
tmconfig (1)
command.
ubbconfig (5),
tmloadcf (1),
tmconfig (1)
See message 728 for an explanation.
See message 728 for an explanation.
An attempt to delete an entry from the internal TUXEDO System/T queue table failed
while attempting to delete one of the servers associated with the queue.
This should not happen during normal system operation.
Contact your TUXEDO System Technical Support.
One of the internal routines to manage TUXEDO System/T data structures received an
invalid service table parameter.
This should not occur during normal system operation.
Contact your TUXEDO System Technical Support.
One of the internal routines to manage TUXEDO System/T data structures received an
invalid server table parameter.
This should not occur during normal system operation.
Contact your TUXEDO System Technical Support.
The TUXEDO System/T bulletin board data structures contain an invalid service/server
association. This indicates a corruption of data structures and should
not occur during normal system operation.
Contact your TUXEDO System Technical Support.
The function used to perform data dependent routing during a service
call returned an error. If using the TUXEDO System/T supplied routing functions,
a previous userlog message will give more specifics as to the cause of the
error. If the application administrator modified the buffer type switch
to add additional routing functions, a previous userlog message may or
may not be present.
Refer to the previous message in the userlog for more information on the
cause of the error.
ubbconfig (5),
tuxtypes (5)
The function used to perform data dependent routing during a service
call indicated that the current data is to be routed to a group name that
does not exist.
If using the routing functions for TUXEDO System/T supplied types, this should not happen.
Contact your TUXEDO System Technical Support.
The service
service_name
is not offered as part of group
group_name.
This message may occur when the routing criterion associated with service
service_name
specifies one or more groups in which the service is not currently offered.
Examine the routing criterion associated with
service_name
in the configuration file.
Make certain that service
service_name
is offered in each group listed in the routing criterion.
If the service is temporarily not available in a particular group,
start the server(s) that offers
service_name
in that group.
If
service_name
is not meant to be offered in a particular group, modify the routing
criterion so that that group is no longer listed.
The process producing this error message is not attached to the
TUXEDO System/T configuration.
If this message occurred in a client process, make sure that
the process successfully invokes
tpinit ()
before issuing any other System/T calls (with the exception of calls
noted as being specifically allowed prior to
tpinit ()).
If the error occurred within an administrative process or a server process,
contact your TUXEDO System Technical Support.
See message 744 for an explanation.
See message 744 for an explanation.
A process was unable to lock the TUXEDO System/T shared memory data structures.
Contact your TUXEDO System Technical Support.
See message 744 for an explanation.
See message 744 for an explanation.
The process was unable to successfully unlock the TUXEDO System/T Bulletin Board.
As a result of this problem, other processes will be unable to lock the
Bulletin Board.
The most common cause of this error is the accidental removal of some
or all of the TUXEDO System/T semaphore sets.
Ask the privileged users on your system (normally the TUXEDO System/T administrator and
root )
whether they may have accidentally removed some IPC resources, perhaps
through inadvertent use of the UNIX System
ipcrm (1)
command. If no IPC resources have been accidentally removed,
contact your TUXEDO System Technical Support.
The process attempted to unlock the TUXEDO System/T Bulletin Board,
but it was not the locker of the Bulletin Board. Because of this,
no change was made to the status of the Bulletin Board.
Contact your TUXEDO System Technical Support.
700 ERROR: Invalid search key
DESCRIPTION
ACTION
701 ERROR: [Parameter error in internal routine]
DESCRIPTION
ACTION
703 ERROR: Cannot get statistics on message queue number
DESCRIPTION
ACTION
704 ERROR: Operating system parameter for message queues too small
DESCRIPTION
ACTION
SEE ALSO
705 ERROR: No BRIDGE available for remote send
DESCRIPTION
ACTION
709 ERROR: Memory allocation failure
DESCRIPTION
ACTION
710 ERROR: Server table index out of range
DESCRIPTION
ACTION
711 ERROR: Server table index out of range
DESCRIPTION
ACTION
712 ERROR: Memory allocation failure
DESCRIPTION
ACTION
713 ERROR: Queue parameter error in internal routine
DESCRIPTION
ACTION
715 ERROR: Cannot attach bulletin board - magic number mismatch
DESCRIPTION
ACTION
716 ERROR: Cannot attach bulletin board - wrong release of software
DESCRIPTION
ACTION
SEE ALSO
717 ERROR: Cannot attach to or create shared memory
DESCRIPTION
ACTION
721 ERROR: Server group creation failure
DESCRIPTION
ACTION
722 ERROR: Cannot add subtype to bulletin board
DESCRIPTION
ACTION
723 ERROR: Cannot add subtype: no more room in subtype table
DESCRIPTION
ACTION
724 ERROR: Service information invalid
DESCRIPTION
ACTION
725 ERROR: Server information invalid, does not exist
DESCRIPTION
ACTION
726 ERROR: Server information invalid, does not exist
DESCRIPTION
ACTION
727 ERROR: [Server parameter error in internal routine]
DESCRIPTION
ACTION
728 ERROR: [Queue parameter error in internal routine]
DESCRIPTION
ACTION
729 ERROR: Server not available, doing work
DESCRIPTION
ACTION
730 ERROR: No space for another queue table entry
DESCRIPTION
ACTION
SEE ALSO
732 ERROR: BBL unstable or dead
DESCRIPTION
ACTION
733 ERROR: [Type information invalid]
DESCRIPTION
ACTION
734 ERROR: Cannot add to type table due to lack of space
DESCRIPTION
ACTION
SEE ALSO
735 ERROR: [Queue parameter error in internal routine]
DESCRIPTION
ACTION
736 ERROR: [Cannot delete entry from queue table due to invalid server association]
DESCRIPTION
ACTION
737 ERROR: [Invalid service information passed to internal routine]
DESCRIPTION
ACTION
738 ERROR: [Invalid server information passed to internal routine]
DESCRIPTION
ACTION
739 ERROR: [Inconsistent service/server associations in bulletin board]
DESCRIPTION
ACTION
741 ERROR: Routing function failed
DESCRIPTION
ACTION
SEE ALSO
742 ERROR: Unknown group name returned from routing function
DESCRIPTION
ACTION
743 ERROR: No service 'service_name' in group 'group_name'
DESCRIPTION
ACTION
744 ERROR: Not attached to a Bulletin Board
DESCRIPTION
ACTION
745 ERROR: Process not attached to a Bulletin Board
DESCRIPTION
ACTION
746 ERROR: Cannot lock Bulletin Board
DESCRIPTION
ACTION
747 ERROR: Process not attached to Bulletin Board
DESCRIPTION
ACTION
748 ERROR: Cannot unlock Bulletin Board
DESCRIPTION
ACTION
749 ERROR: Cannot unlock Bulletin Board, not the locker
DESCRIPTION
ACTION
751 ERROR: semop system call failure for semaphore semno, errno = errno_val