LIBTUX Messages 200-299
200 ERROR: Invalid service information
given
Description
The
service requested to be unadvertised is invalid.
Action Contact
your BEA TUXEDO system Technical Support.
See Also
tpunadvertise(3c)
201 ERROR: Memory allocation failure
Description
An
attempt dynamically to allocate memory from the operating system using malloc() failed.
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.
202 ERROR: No bulletin board
Description
The
process is currently not attached to the Bulletin Board so the service cannot
be offered.
Action Contact
your BEA TUXEDO system Technical Support.
203 ERROR: Invalid service information
given, NULL name
Description
Function
called without proper parameters - null service to offer.
Action Contact
your BEA TUXEDO system Technical Support.
205 ERROR: Invalid service information
given, function name too long
Description
Function
called with improper parameters - function name too long.
Action Contact
your BEA TUXEDO system Technical Support.
206 ERROR: Invalid service information
given, bad function address
Description
Function
called with improper parameters - function address cannot be found.
Action Contact
your BEA TUXEDO system Technical Support.
210 ERROR: tmbbclean failed, couldn’t
find DBBL
Description
Could
not find structures/information associated with the DBBL.
Action Contact
your BEA TUXEDO system Technical Support.
211 ERROR: tmbbclean failed, couldn’t
find BBL
Description
Could
not find structures/information associated with the BBL.
Action Contact
your BEA TUXEDO system Technical Support.
212 ERROR: tmbbclean failed, message
send/receive error
Description
Sending
of message to the BBL/DBBL to clean up and check status of local Bulletin Board
failed.
Action Check
prior messages or check if message queue is blocked. If queue is blocked,
system usage could be
heavy
and parameters may need to be tuned.
213 ERROR: Memory allocation failure
Description
An
attempt dynamically to allocate memory from the operating system using malloc() failed while
allocating
space to store tmids.
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.
216 WARN: Process pid died;
removing from BB
Description
The
process that was attached to the BB died, so the BB is cleaning up.
Action No
action required for BB, but you may want to investigate why the process died.
217 WARN: pid=pid died leaving
BB locked; cleaning up
Description
The
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.
218 ERROR: Error cleaning BB owner
1
Description
An
error occurred in cleaning up after a dead process. Either the slot could not
be found, or a prior
message
indicates a semaphore error.
Action Contact
your BEA TUXEDO system Technical Support.
221 ERROR: Error putting ENVFILE filename
into environment
Description
The
server could not process the ENVFILE properly. This includes not being able to
find, open, or read
it.
Action Check
the path of ENVFILE, and the permissions and owner of the file.
See Also
ubbconfig(5)
ERROR: Cannot get service parms for server
Description
The
server could not process the parameters for a service specified in the
TUXCONFIG file. This
includes
a problem with loading the information from the SERVICES section, or not
understanding some
of the
parameters (for example, buffer types.)
Action Check
the SERVICES section of the UBBCONFIG file for correct parameters.
See Also
ubbconfig(5)
223 WARN: Duplicate server
Description
An
instantiation of this server already exists and this is a duplicate. It will
exit gracefully.
Action Check
that the server that you wish to start is correct. If the server died
unexpectedly or is hung, the
process
needs to be killed if hung, and the bulletin board must be given time to clean
up after the killed
process
before starting the server again.
230 ERROR: Buffer type tables not
available
Description
The
process is currently not attached to the Bulletin Board so it could not access
the type switch table.
Action Contact
your BEA TUXEDO system Technical Support.
236 ERROR: Remote tmnwkill timed out count
secs
Description
The
process tried to signal a remote process, and a message was sent to the bridge
process on the remote
side to
perform the fill for it. The reply to indicate the success/failure of the
operation did not return
before
the operation timed out.
Action This
timeout could be a sign of network congestion, but is not a specific network
failure, other than the
operation
did not return in time. If the network is not a problem, then the timeout is
too small for the
speed
with which the signal request can be met.
237 ERROR: semctl err: errno = errno_val,
key = key_val
Description
The
semctl() call
failed. This is possibly due to the semaphore set being removed or differing
permissions
on the semaphore.
Action The
semaphore set was somehow removed. If this does happen, the system will
eventually fail. Contact
your BEA
TUXEDO system Technical Support.
245 WARN: Invalid LMID specification:
PMID=mid
Description
An
erroneous LMID has been specified and an attempt to locate it has failed.
Action Check
and edit the UBBCONFIG file such that all specified LMIDs reference the correct
machine.
See Also
ubbconfig(5)
248 ERROR: System init function failed,
Uunixerr = errno_val
Description
The
server has failed to join the application.
Action See
surrounding messages for reasons for failure to join.
See Also
buildserver(1), servopts(5)
250 ERROR: tpsvrinit() failed
Description
A
call to tpsvrinit() failed.
This may easily be caused by an application-defined tpsvrinit function
returning
failure.
Action Check
prior specific tpsvrinit() messages
or the application specific messages.
See Also
tpsvrinit(3c)
251 ERROR: tpsvrinit() failed with
outstanding message handles
2
Description
A
call to tpsvrinit(),
although returning success, failed to receive all outstanding reply messages
and
therefore has outstanding handles. This is probably caused by an
application-defined tpsvrinit
function.
Action Check
prior specific tpsvrinit() messages
or the application specific messages.
See Also
tpsvrinit(3c)
252 WARN: Cannot synchronize with
tmboot...continuing
Description
The
connection with tmboot was lost by the forking process. If on the same node
where tmboot is
running,
the pipe with tmboot was lost and may be due to the tmboot process being
killed. If on a remote
node,
the pipe to the TAGENT process was lost, which may be due to the TAGENT process
being killed.
Action No
action required, although the cause of tmboot/TAGENT dying should be
investigated if not known.
See Also
tmboot(1)
253 ERROR: Memory allocation failure
Description
An
attempt dynamically to allocate memory from the operating system using malloc() failed while
copying
the arguments to CLOPT as the server tries to join the application.
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.
254 ERROR: Memory allocation failure
Description
An
attempt dynamically to allocate memory from the operating system using malloc() failed while
copying
the arguments to CLOPT as the server tries to join the application.
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.
255 INFO: Duplicate -A option ignored
Description
Multiple
-A options were specified to the server in the CLOPT line of the UBBCONFIG
file.
Action Check
the CLOPT option in the configuration file.
See Also
ubbconfig(5), servopts(5)
256 WARN: Queue address must be numeric
Description
The
queue address, as specified to the server through the -Q option of CLOPT, is
non-numeric.
Action Check
the address specified for the -Q option in the configuration file.
See Also
ubbconfig(5), servopts(5)
257 WARN: Invalid lock argument,
setting to PROCLOCK
Description
The
lock argument, as specified to the server through the -l option in CLOPT, is
invalid. It must be one
of
"’t’ (TEXTLOCK)," "’d’ (DATALOCK)," ’b’ or "’p’
(PROCLOCK)." The argument is ignored and is
set to
’p’ for PROCLOCK.
Action Check
the lock argument for the -l option in CLOPT in the configuration file.
See Also
ubbconfig(5), servopts(5) in the System/T reference manual, plock(2) in UNIX system reference
manuals
258 WARN: Memory lock plock() failed
Description
An
attempt to lock the process in core has failed. This was requested by setting
the lock option, -l, on the
CLOPT
option to the server in the configuration file. The error can occur when the
server not being run
as
super-user, the requested lock is already on the process, or the system is out
of memory.
Action Make
sure the server is being started as super-user (and that the tmboot process is
running as super-user).
If the
application can run its own code (tpsvrinit())
first, it might also have put a lock on the
process.
See Also
ubbconfig(5), servopts(5) in the System/T reference manual, plock(2) in UNIX system reference
manuals
259 WARN: nice() failed
3
Description
An
attempt to change the priority of the process has failed. This was requested by
setting the -n option on
the
CLOPT option to the server in the configuration file. This can be caused by the
option to -n being
negative
or greater than 39, and not super-user.
Action Check
that the argument to the -e option of CLOPT is correct in the configuration
file.
See Also
ubbconfig(5), servopts(5) in the System/T reference manual, nice(2) in UNIX system reference
manuals
260 WARN: Cannot open path as
stderr, Uunixerr = Uunixerr
Description
An
attempt to open the file for stderr failed. This file may have been specified
by the -e option on the
CLOPT
option to the server in the configuration file. This can be caused by the
inability to access the
path
given as the argument to the -e option.
Action Check
that the argument to the -e option of CLOPT is correct in the configuration
file.
See Also
ubbconfig(5), servopts(5)
261 WARN: Cannot open path as
stdout: Uunixerr = Uunixerr
Description
An
attempt to open the file for stout failed. This file may have been specified by
the -o option on the
CLOPT
option to the server in the configuration file. This can be caused by the
inability to access the
path
given as the argument to the -o option.
Action Check
that the argument to the -o option of CLOPT is correct in the configuration
file.
See Also
ubbconfig(5), servopts(5)
262 INFO: Standard main starting
Description
The
arguments have been successfully processed, and joining the application will
continue.
Action No
action required.
263 ERROR: Memory allocation failure
Description
An
attempt dynamically to allocate memory from the operating system using malloc() failed while
setting
up buffers to advertise the services of the application as the server tries to
join the application.
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.
264 ERROR: Cannot set server group/id
Description
This
cannot happen because code changed to use a local variable, not a passed-in
variable.
Action Contact
your BEA TUXEDO system Technical Support.
267 INFO: Duplicate advertisement of
service svcname ignored
Description
A
request to advertise the same service a second time is ignored.
Action Check
the configuration file for multiple occurrences of the service on the -s
option.
See Also
ubbconfig(5), servopts(5)
268 ERROR: Failed to stop serving
Description
The
server did not properly shut down.
Action There
may be prior messages to describe the problem. In any case, the BBL should
clean up after the
process.
270 ERROR: Restart sync error errno
Description
An
internal error occurred during a restart of a process. An acknowledgment that
the process was
restarted
was never received.
Action Contact
your BEA TUXEDO system Technical Support.
271 ERROR: System lock semop failure,
key = key (errno = errno)
Description
In
an attempt to lock the bulletin board, a call to semop(2) failed.
Action Examine
the value returned in the UNIX System errno, and attempt to fix the
problem described by the
errno.
If unable to do so, contact your BEA TUXEDO system Technical Support.
272 ERROR: System unlock semop failure,
key = key (errno = errno)
Description
In
an attempt to unlock the bulletin board, a call to semop(2) failed.
Action Examine
the value returned in the UNIX System errno and attempt to fix the problem
described by the
errno.
If unable to do so, contact your BEA TUXEDO system Technical Support.
294 ERROR: function: FSCONFIG
not or incorrectly set
4
Description
The
variable FSCONFIG is either not set or has been incorrectly set.
Action Check
and edit the UBBCONFIG file and make sure the FSCONFIG environment variable is
set
correctly.
See Also
ubbconfig(5)
295 ERROR: funcname: corrupted
VTOC or different release
Description
An
attempt to access the VTOC has failed because the existing VTOC has either been
corrupted or was
created
by a different release of the TUXEDO System.
Action Contact
your BEA TUXEDO system Technical Support.
296 ERROR: funcname: VTOC not
initialized
Description
An
attempt to access the VTOC has failed because the existing VTOC has not been
properly initialized.
Action Contact
your BEA TUXEDO system Technical Support.
297 ERROR: funcname: no space
can be allocated for disk table or for VTOC/UDL
Description
An
attempt to allocate space within the VTOC has failed because there are no more
available slots.
Action Contact
your BEA TUXEDO system Technical Support.
298 ERROR: funcname: Read beyond
initialized file boundary.
Description
An
attempt to access information in the VTOC has failed because the read has gone
past the set
boundaries
of the VTOC.
Action Contact
your BEA TUXEDO system Technical Support.
299 ERROR: funcname: Write
beyond initialized file boundary.
Description
An
attempt to write information to the VTOC has failed because the write has gone
past the set
boundaries
of the VTOC.
Action Contact
your BEA TUXEDO system Technical Support.
LIBTUX Messages 300-399
300 ERROR: funcname: UNIX sys
call error - errno_val
Description
An
attempt to access the VTOC through a system call such as open(2), lseek(2),
read(2), write(2),
stat(2),
or unlink(2) has failed because the system
call returned the errno indicated in the message.
Action Contact
your BEA TUXEDO system Technical Support.
301 ERROR: funcname: cannot free
space
Description
An
attempt to free space that was allocated in the VTOC has failed because there
are no more available
VTOC map
entries.
Action Contact
your BEA TUXEDO system Technical Support.
302 ERROR: funcname: bad table
name specified
Description
An
error occurred while either creating a new table entry or accessing an existing
table entry in the
VTOC. If
the error occurred while attempting to create a table, either the table name
already exists, or the
name has
a length of 0 or is greater than the allowable table name size
(GP_LOGICAL_NAME). If the
error
occurred while attempting to access an existing table, either the name doesn’t
exist, or the name has
a length
of 0 or is greater than the allowable table name size.
Action Contact
your BEA TUXEDO system Technical Support.
303 ERROR: funcname: invalid
arguments or request to function
Description
An
error occurred because the indicated function was invoked with invalid
arguments.
Action Contact
your BEA TUXEDO system Technical Support.
304 ERROR: funcname: bad device
name or index specified
Description
An
attempt to access a device has failed because the name used was either of
length 0 or was longer than
the
allowable length of GP_LOGICAL_NAME.
Action Contact
your BEA TUXEDO system Technical Support.
305 ERROR: funcname: attempt to
create overlapping devices
Description
An
error has occurred because of an overlap in devices. An overlap occurs if the
new device begins
before
the old device ends and the new device ends after the old device begins.
Action Contact
your BEA TUXEDO system Technical Support.
306 ERROR: funcname: no entry
remains to create device or table or open table
Description
An
attempt to either create a device or table, or open a table has failed because
there are no more
available
slots in the device list.
Action Contact
your BEA TUXEDO system Technical Support.
308 ERROR: funcname: bad device
type (not character special or regular)
Description
An
attempt to create a disk entry has failed because an invalid device type has
been specified. The only
two
available device types are character special and regular.
Action Contact
your BEA TUXEDO system Technical Support.
309 ERROR: funcname: cannot
obtain lock on VTOC
Description
An
error has occurred because within the function _gp_vtoc_lock(),
an attempt to obtain a lock on
the VTOC
has failed.
Action Contact
your BEA TUXEDO system Technical Support.
310 ERROR: errcode: unknown vtoc
error code
Description
An
error has occurred during an access of the VTOC and has resulted in the
indicated unrecognizable
error
code being returned.
Action Contact
your BEA TUXEDO system Technical Support.
311 ERROR: Cannot locate free block in
tlog
Description
An
attempt to locate and write to a free block in the transaction log has failed.
Action Retry
the operation and if the problem persists, contact your BEA TUXEDO system
Technical Support.
312 ERROR: Transaction log wrong page
number
6
Description
An
attempt to access particular page of the transaction log has failed because the
referenced page is
outside
of the bounds of the transaction log.
Action Retry
the operation and if the problem persists, contact your BEA TUXEDO system
Technical Support.
313 ERROR: Log warmstart can only be
called by BBL
Description
An
attempt to warmstart has failed because only the BBL is allowed to initiate
warmstarts.
Action Contact
your BEA TUXEDO system Technical Support.
314 INFO: Page page skipped,
chksum didn’t match
Description
The
indicated page was skipped while doing a warmstart because the checksum did not
match.
Action No
action required.
315 ERROR: TLOG not in an
understandable format. Different release
Description
The
format of the transaction log is unrecognizable. The release of the software is
different than the
release
of the transaction log.
Action Contact
your BEA TUXEDO system Technical Support.
316 ERROR: Transaction log file exists
Description
An
attempt to create the transaction log has failed because a transaction log
already exists.
Action If
a transaction log exists, remove it and retry the desired operation. If the
problem persists, contact your
BEA
TUXEDO system Technical Support.
317 ERROR: Log start can only be called
by BBL or TMS
Description
A
call to internal function _tlog_start() has failed because the caller is
neither the BBL nor the TMS.
Action Contact
your BEA TUXEDO system Technical Support.
318 ERROR: Log start cannot get tlog
information
Description
An
error occurred in attempting to open the transaction log. Either the *MACHINES
section of the
configuration
file could not be opened, or the current machine id has not been defined in
that
configuration
file.
Action Check
and ensure the accuracy of the TUXCONFIG file, and if the problem persists,
contact your BEA
TUXEDO
system Technical Support.
319 ERROR: Log start cannot open tlog
Description
An
error occurred attempting to open the transaction log with read and write
access.
Action Check
and ensure that the appropriate permissions are set on the transaction log and
on the directory in
which
the transaction log resides. If the problem persists, contact your BEA TUXEDO
system Technical
Support.
320 ERROR: BB TLOGSIZE differs
from number of pages in TLOG file
Description
An
error has occurred opening the transaction log because the actual size of the
TLOG differs from the
size
maintained by the BB.
Action Retry
the desired operation, and if the problem persists, contact your BEA TUXEDO
system Technical
Support.
327 ERROR: Invalid table type desired
Description
An
internal function has failed because it attempted to access an invalid table.
Action Contact
your BEA TUXEDO system Technical Support.
328 ERROR: No space in Bulletin Board
for tablename
Description
An
attempt to allocate a free entry in the Bulletin Board for tablename has
failed because it is full.
Action Re-configure
the application to increase the size of the associated table.
329 ERROR: Tried to free non-alloced
tmrte
Description
An
attempt to free a registry table entry has failed because the table entry has
not yet been allocated.
Action Contact
your BEA TUXEDO system Technical Support.
330 ERROR: Invalid table type given
Description
An
internal function has failed because it attempted to access an invalid table.
Action Contact
your BEA TUXEDO system Technical Support.
331 ERROR: No registry table entries
7
Description
There
are no more free entries in the registry table, so an attempt to allocate an
entry has failed.
Action Contact
your BEA TUXEDO system Technical Support.
332 ERROR: Memory allocation failure
Description
An
attempt dynamically to allocate memory from the operating system using malloc()
failed. This
message
is issued when a system process (for example, DBBL or BBL) initializes and its
call to
malloc()
fails.
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.
See Also
ulimit(2) in UNIX system reference
manuals
333 ERROR: No DBBL
Description
A
program was booted in an MP configuration without the Bulletin Board existing.
Action Clean
up any IPC resources and re-boot the application from scratch.
See Also
tmboot(1)
334 ERROR: No BBL
Description
A
program was booted without the Bulletin Board existing.
Action Clean
up any IPC resources and re-boot the application from scratch.
See Also
tmboot(1)
335 ERROR: Wrong bulletin board type or
IPCKEY not unique
Description
Either
the bulletin board type has been changed for this application and the old
bulletin board (in shared
memory)
still exists, or the IPCKEY for the application being booted is not unique
(another application is
using
the same IPCKEY and has attached to shared memory using that IPCKEY as the
shared memory
id).
Action Edit
the UBBCONFIG configuration file, change the IPCKEY to a unique value, reload
the
TUXCONFIG
using tmloadcf, and reboot the application.
See Also
tmloadcf(1), ubbconfig(5)
336 ERROR: semget err: errno=errno_val,
key = key_val
Description
While
initializing the application, a system semaphore could not be created.
Action Look
up the errno_val in errno.h to see its name. There are several possible
causes. ENOSPC indicates
that not
enough semaphores are configured in the operating system; re-configure the OS
to have more
semaphore
identifiers or sets. EACCES indicates that the user executing the command does
not have
permissions,
which could be due to another application using the same ICPKEY. Check the
owner of the
semaphore
using the key_val and the ipcs(1)
command, and change IPCKEY if necessary.
337 ERROR: semctl err: errno=errno_val,
key=key_val, id=id_val
Description
While
initializing the application, the status of a system semaphore could not be
obtained.
Action Look
up the errno_val in errno.h to see its name. There are several possible
causes. EACCES indicates
that the
user executing the command does not have permissions, which could be due to
another
application
using the same ICPKEY. Check the owner of the semaphore using the key_val and
the
ipcs(1)
command. EINVAL could indicate that the semaphore was destroyed during shutdown
of the
system
while another user tried to activate the system.
338 ERROR: BB semaphore not initialized
within 10 seconds (key=0xkey_val).
Description
While
initializing the application, a program found the BEA TUXEDO system semaphore
existed but
was not
initialized within 10 seconds.
Action Use
the ipcs(1) command to check the specified
key value, checking the creator process to see if it is
alive.
Remove the IPC resources and re-boot the application.
339 ERROR: Creating process may be
dead; manual intervention required.
Description
While
initializing the application, a program found the BEA TUXEDO system semaphore
existed but
was not
initialized within 10 seconds. This is related to message 338.
Action Use
the ipcs(1) command to check the specified
key value, checking the creator process to see if it is
alive.
Remove the IPC resources and re-boot the application.
340 ERROR: Wrong configuration file
8
Description
Either
the configuration parameters have been changed for this application and the old
bulletin board (in
shared
memory) still exists, or the IPCKEY for the application being booted is not
unique (another
application
is using the same IPCKEY and has attached to shared memory using that IPCKEY as
the
shared
memory id).
Action Edit
the UBBCONFIG configuration file, change the IPCKEY to a unique value, reload
the
TUXCONFIG
using tmloadcf, and reboot the application.
See Also
tmloadcf(1), ubbconfig(5)
341 ERROR: Could not allocate bulletin
board shared memory
Description
While
initializing the BEA TUXEDO application, shared memory could not be allocated
for the Bulletin
Board.
Action Check
that the IPCKEY in the UBBCONFIG configuration file is not being used by
another application
for
shared memory. Check that enough shared memory has been configured.
See Also
tmloadcf(1), ubbconfig(5)
342 ERROR: Could not allocate bulletin
board shared memory
Description
While
initializing the BEA TUXEDO application, shared memory could not be allocated
for the Bulletin
Board.
Action Check
that the IPCKEY in the UBBCONFIG configuration file is not being used by
another application
for
shared memory. Check that enough shared memory has been configured.
See Also
tmloadcf(1), ubbconfig(5)
343 ERROR: Could not find DBBL
Description
While
initializing the BEA TUXEDO application, shared memory could not be allocated
for the Bulletin
Board.
Action The
application is configured as mode MP and the DBBL has not created the BB. Make
sure that the
DBBL is
booted first and did not die. Check that the IPCKEY in the UBBCONFIG
configuration file is
not
being used by another application for shared memory. Check that enough shared
memory has been
configured.
See Also tmloadcf(1), ubbconfig(5)
344 ERROR: Could not allocate bulletin
board shared memory
Description
While
initializing the BEA TUXEDO application, shared memory could not be allocated
for the Bulletin
Board.
Action Check
that the IPCKEY in the UBBCONFIG configuration file is not being used by
another application
for
shared memory. Check that enough shared memory has been configured.
See Also
tmloadcf(1), ubbconfig(5)
345 ERROR: Cannot find DBBL
Description
An
attempt was made to send a message to the DBBL and its whereabouts could not be
ascertained either
from the
BB or from a BRIDGE process.
Action Check
for a partitioned network, corrupted shared memory, or if all administrative
processes are running.
346 ERROR: Not a Bulletin Board
Description
The
BEA TUXEDO system application’s IPCKEY is clashing with another application’s
use of UNIX
IPC
resources, specifically with a UNIX IPC semaphore.
Action Choose
another IPCKEY for your BEA TUXEDO system application.
See Also
tmadmin(1)
347 ERROR: Bulletin Board version
mismatch
Description
The
process trying to attach to the Bulletin Board differs in release from the
Bulletin Board creator. The
process
fails to join the application.
Action Make
sure that $TUXDIR/bin points to the most current release of the BEA TUXEDO
System. Also,
make
sure application processes have been re-linked or re-compiled with the latest
release.
349 ERROR: Memory allocation failure
9
Description
An
attempt dynamically to allocate memory from the operating system using malloc() failed. This
message
is issued when a system process (for example, DBBL or BBL) initializes and its
call to
malloc()
fails.
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.
See Also
ulimit(2) in UNIX system reference
manuals
350 ERROR: Configuration file
parameters do not match existing bulletin board.
Description
When
a process initially tries to join the application, this message is issued when
the process’
configuration
file parameters do not match the existing bulletin board. This could happen,
for example, if
the
application’s ubbconfig file is modified and re-loaded with tmloadcf.
Action Make
sure that your TUXCONFIG file matches that with which the system was
initialized.
See Also
tmloadcf(1)
351 ERROR: Error building node tables
Description
When
a BBL initializes, it populates certain areas of the bulletin board. This
message is issued when a
BBL
encounters an error creating the node table in the bulletin board. The node
table contains entries for
the
machines in the *MACHINES section of the ubbconfig file. This error occurs when
a node is running
with a
pre-4.2.1 release of the BEA TUXEDO system. Releases before 4.2.1 supported at
most 50 nodes
in an
application.
Action If
your application contains more than 50 nodes specified in your ubbconfig file,
then all nodes in the
application
must be release 4.2.1 or higher.
See Also
ubbconfig(5)
352 ERROR: Error resetting ULOGPFX
Description
The
program failed to set the prefix for the userlog file either because dynamic
space allocation failed or
because
the TUXCONFIG file was corrupted. The userlog prefix will be $APPDIR/ULOG.
Action If
other messages in the userlog indicate that the TUXCONFIG file is corrupted,
you should re-load the
TUXCONFIG
file at your earliest convenience. If other messages in the userlog indicate
that your system
is out
of memory, then ensure that 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.
See Also
ubbconfig(5), ulimit(2) in UNIX system reference manuals
353 ERROR: Error putting ENVFILE file
into environment
Description
This
message is issued when an error occurs putting the process’ ENVFILE into its
environment.
Action See
the userlog for other messages that explain exactly which error occurred as
part of processing the
process’
ENVFILE.
See Also
ubbconfig(5)
354 WARN: Error changing directory to
appdir (path) for LMID (lmid)
Description
When
this message is issued, an invalid APPDIR pathname is specified in the
*MACHINES section for
the LMID
shown in the message. The processes associated with this LMID will use the
default APPDIR
for this
TUXCONFIG.
Action At
your earliest convenience, you should set APPDIR to a valid pathname and
re-load your
TUXCONFIG
with tmloadcf.
See Also
tmloadcf(1), ubbconfig(5)
355 ERROR: No BBL on this machine
Description
The
process that issued this message tried to join a site that was in the midst of
being shut down.
Action No action required.
356 ERROR: Reached UNIX limit on
semaphore ids
Description
The
BBL could not create any more semaphore ids because the UNIX system-imposed
limit on the
maximum
number of allowed semaphores system-wide would be exceeded.
Action Contact
your BEA TUXEDO system Technical Support about resetting the number of UNIX
semaphores
as per
the IPC tuning guidelines in the BEA TUXEDO Installation Guide.
See Also
BEA TUXEDO Installation Guide
357 ERROR: Cannot create enough
semaphores for BB, (UNIX limit), MAXACCESSERS too high
10
Description
When
a BBL initializes, it creates one or more sets of semaphores for serializing
access to the bulletin
board.
The number of semaphores created per machine is roughly equal to the value of
MAXACCESSERS
on that machine. This message is printed when the BBL cannot create as many
semaphores
as it needs.
Action If
possible, decrease the value of MAXACCESSERS for the machine. If several
machines are used in
your
application, it is advisable to specify for each *MACHINES section entry a
MAXACCESSERS
value
that is roughly the number of System/T client and server processes that will
run simultaneously on
that
machine.
See Also ubbconfig(5)
358 ERROR: Reached UNIX limit on
semaphore ids
Description
The
BBL could not create any more semaphore ids because the UNIX system-imposed
limit on the
maximum
number of allowed semaphores system-wide would be exceeded.
Action Contact
your BEA TUXEDO system Technical Support about resetting the number of UNIX
system
semaphores
as per the IPC tuning guidelines in the BEA TUXEDO Installation Guide.
See Also
BEA TUXEDO Installation Guide
359 ERROR: Cannot create enough
semaphores for BB, (UNIX limit), MAXACCESSERS too high
Description
When
a BBL initializes, it creates one or more sets of semaphores for serializing
access to the bulletin
board.
The number of semaphores created per machine is roughly equal to the value of
MAXACCESSERS
on that machine. This message is printed when the BBL cannot create as many
semaphores
as it needs.
Action If
possible, decrease the value of MAXACCESSERS for the machine. If several
machines are used in
your
application, it is advisable to specify for each *MACHINES section entry a
MAXACCESSERS
value
that is roughly the number of System/T client and server processes that will
run simultaneously on
that
machine.
See Also
ubbconfig(5)
360 ERROR: semctl for initializing sems
failed: errno
Description
Once
the BBL creates a semaphore set used for serializing access to the BB, it
initializes it. This message
is
issued when the BBL fails to initialize a semaphore set as locked. The issued
message contains the
UNIX
system error number, errno, which can be used to determine the exact
nature of the error.
Action Contact
your BEA TUXEDO system Technical Support.
See Also
semctl(2) in UNIX system reference
manuals
361 ERROR: semctl for initializing sems
failed: errno
Description
Once
the BBL creates a semaphore set used for serializing access to the BB, it
initializes it. This message
is
issued when the BBL fails to initialize a semaphore set with the
administrator’s UNIX uid, gid, and
permissions
as specified in the ubbconfig file. The issued message contains the UNIX system
error
number, errno,
which can be used to determine the exact nature of the error.
Action Contact
your BEA TUXEDO system Technical Support.
See Also
semctl(2) in UNIX system reference
manuals
362 ERROR: TPEOS time set errno errno
Description
As
part of initializing the global transaction table, the BBL calls the time() system call. This message
is
issued when the call to time() fails.
The message includes the error number, errno, which can be
used to
determine the exact nature of the error.
Action Consult
the time(2) manual page to determine the
exact nature of the error.
See Also
time(2) in UNIX system reference
manuals
364 ERROR: Failure during send/receive
of remote procedure call
Description
An
internal error occurred while attempting to send a remote procedure call.
Action Check
that the DBBL is running, and retry the desired operation. If the error occurs
again, contact your
BEA
TUXEDO system Technical Support.
370 ERROR: Error setting time for
transaction counter, errno errno
Description
As
part of starting a new transaction, the time()
system
call is issued. This message is issued when the
call to time() fails. The message includes the error
number, errno, which can be used to determine the
exact
nature of the error.
Action Consult
the time(2) manual page to determine the
exact nature of the error.
See Also
time(2) in UNIX system reference
manuals
11
376 ERROR: tpabort: xa_rollback
returned status
Description
This
message is issued if the process aborting a transaction encounters an error upon
calling the database
resource
manager with xa_rollback().
The message prints the error code that the function returned.
Action Contact
your BEA TUXEDO system Technical Support or your database system vendor. See
the userlog
for more
information on the outcome of the transaction. Also, use tmadmin’s printtrans
command to find
out more
information about the transaction.
See Also
tmadmin(1)
377 ERROR: tpabort state state
Description
This
message is issued when a transaction is being aborted and the state of the
transaction is such that the
normal
procedure for aborting the transaction could not be followed. The state of the
transaction is
printed
as part of this message. If the state is TMGABORTED, then the transaction has
already been
aborted;
all other states reflect the various stages of two-phase commitment (including
heuristic
outcomes).
Action See
the userlog for more information about this transaction’s completion. Also, use
tmadmin’s printtrans
command
to find out more information about the transaction.
See Also
tmadmin(1)
378 ERROR: Failed to determine uname
Description
An
attempt to determine the machine id through a call to uname(2)
has failed.
Action Make
sure the machine’s uname is correctly configured. Retry the desired operation;
if the error occurs
again,
contact your BEA TUXEDO system Technical Support.
381 ERROR: Cannot call ATMI routines
until you have joined system
Description
This
message is issued if tpforward() is
called outside of a service routine (for example, by a client).
Action Change
your application code to not use tpforward() in
clients or outside of service routines.
See Also
tpforward(3c)
382 ERROR: Performed tpforward() with
outstanding replies
Description
This
message is issued when a service routine calls tpforward()
with
outstanding replies. The client
that
invoked this service routine receives an error, TPESVCERR, from either tpcall() or
tpgetrply(),
if it was expecting a reply. The service named by tpforward()
is
not invoked.
Action You
should alter your service routine to call either tpgetrply()
or
tpcancel() for all
outstanding
replies
before calling tpforward().
If your service routine encounters an application error and you
need to
return from the service immediately, then use tpreturn()
with
TPFAIL.
See Also
tpcancel(3c), tpgetrply(3c),
tpforward(3c), tpreturn(3c)
389 WARN: Failed to set priority for
TMS request
Description
When
a request is sent to the TMS to complete a transaction, the priority of the
request is set to optimize
performance.
This message is issued as a warning when the system fails to override the
default priority.
The
request is sent at the default priority.
Action No
action required.
390 ERROR: tpcommit msg failure, check
GTT
Description
This
message is issued when the system encounters an error trying to receive the
reply to a request sent to
a TMS to
complete a transaction. This message is typically issued when a system-level
failure occurs.
Action See
the userlog for more information about this transaction’s completion and about
any communication
error
that may have occurred. Also, use tmadmin’s printtrans command to find out more
information
about
the transaction and use the printnet command to see the status of all machine connections
in the
network.
This command will report any network partitions.
See Also
tmadmin(1)
391 ERROR: No room to add group name
Description
This
message is issued when a transaction has visited more than 16 BEA TUXEDO system
groups (as
defined
in the GROUPS section of the ubbconfig file). At that point, the transaction
will not continue to
propagate
nor will it complete successfully.
Action Consider
combining groups or using data dependent routing to consolidate requests to
servers within the
same group
in order to allow your transaction to stay within the 16 group maximum.
See Also
ubbconfig(5)
392 INFO: GTTELOG: GTRID: machine(machine)
counter_time(0xtime) counter(0xcount)
12
Description
This
message prints out the contents of a global transaction table entry. This
includes the transaction
identifier
(GTRID), the transaction’s state, and other pertinent information that can be
used by support
personnel
to help locate problems with global transactions.
Action No
action required.
See Also
See
Messages No. 393, 394, 395, and 396 in this chapter, and Message No. 408 in the
chapter on
CMDTUX
messages.
393 INFO: coordinator(group)
group_count(count) tran_state(state)
Description
This
message is a continuation of message 392 in this chapter.
Action No
action required.
See Also
See
Messages No. 392, 394, 395, and 396 in this chapter, and Message No. 408 in the
chapter on
CMDTUX
messages.
394 INFO: cmchid(val) q(val2)
type(val3) iter(val4) reg_index(val5)
Description
This
message is a continuation of message 392 in this chapter.
Action No
action required.
See Also
See
Messages No. 392, 393, 395, and 396 in this chapter, and Message No. 408 in the
chapter on
CMDTUX
messages.
395 INFO: log_page(val) version(val2)
tranflags(val3)
Description
This
message is a continuation of message 392 in this chapter.
Action No
action required.
See Also
See
Messages No. 392, 393, 394, and 396 in this chapter, and Message No. 408 in the
chapter on
CMDTUX
messages.
396 INFO: GR[val]:name(val1)local(val2)state(val3)
Description
This
message is a continuation of message 392 in this chapter.
Action No
action required.
See Also
See
Messages No. 392, 393, 394, and 395 in this chapter, and Message No. 408 in the
chapter on
CMDTUX
messages.
397 ERROR: Cannot allocate entry on GTT
Description
This
message is issued when no more room exists in the bulletin board to accommodate
transactions.
This
message can occur for a new transaction, in which case the transaction will
fail to begin. Or, this
message
can occur when an existing transaction tries to instantiate itself on a
server’s bulletin board, in
which
case the transaction will fail to commit. This message might reflect a
transient condition based on
a large,
"bursty" transaction volume.
Action Consider
increasing the MAXGTT entry in your application’s ubbconfig file if this
message occurs often
or if
too many transactions fail due to the current MAXGTT setting. If you are
already using the
maximum
value, and if you are also using either the LOGGED value for the CMTRET keyword
in the
ubbconfig
file or the TP_CMT_LOGGED setting for tpscmt(3c),
then use the COMPLETE or
TP_CMT_COMPLETE
settings, respectively, so that new transactions will not start until current
ones
complete.
See Also
tpscmt(3c), tx_set_commit_return(3c),
ubbconfig(5)
398 ERROR: Cannot allocate entry on
GTT, TMID creation failed
Description
This
message is issued when no more room exists in the bulletin board to accommodate
transactions.
This
message can occur for a new transaction, in which case the transaction will
fail to begin. Or, this
message
can occur when an existing transaction tries to instantiate itself on a
server’s bulletin board, in
which
case the transaction will fail to commit. This message might reflect a
transient condition based on
a large,
"bursty" transaction volume.
Action Consider
increasing the MAXGTT entry in your application’s ubbconfig file if this
message occurs often
or if
too many transactions fail due to the current MAXGTT setting. If you are
already using the
maximum
value, and if you are also using either the LOGGED value for the CMTRET keyword
in the
ubbconfig
file or the TP_CMT_LOGGED setting for tpscmt(3c),
then use the COMPLETE or
TP_CMT_COMPLETE
settings, respectively, so that new transactions will not start until current
ones
complete.
See Also
tpscmt(3c), tx_set_commit_return(3c),
ubbconfig(5)
399 ERROR: xa_forget returned status
13
Description
When
a database resource manager (RM) makes a unilateral decision to complete a
global transaction
and its
decision is in conflict with the BEA TUXEDO system’s decision, this situation
is known as a
"heuristic
decision". The RM is required to log on stable storage this decision until
the BEA TUXEDO
system
explicitly tells the RM to forget its decision. This error message is issued
when the RM
encounters
an error while processing the "forget" request.
Action Contact
your BEA TUXEDO system Technical Support or your database system vendor.
14
LIBTUX Messages 400-499
400 ERROR: Invalid arguments for
getting acknowledgement
Description
This
message is issued when an internal BEA TUXEDO system routine is passed invalid
arguments.
Action Contact
your BEA TUXEDO system Technical Support.
401 ERROR: Could not find DBBL
Description
An
attempt was made to send a message to the DBBL and its whereabouts could not be
ascertained either
from the
BB or from a BRIDGE process.
Action Check
for a partitioned network, corrupted shared memory, or if all administrative
processes are running.
403 ERROR: Received message with an
unknown internal type index val
Description
While
processing a reply, the internal buffer type is unknown. This refers to an
internal system problem
that
could be caused, for example, by corrupted shared memory.
Action Contact
your BEA TUXEDO system Technical Support.
404 ERROR: Received message of unknown
type ’type’ subtype ’subtype’
Description
The
process received a message whose type and subtype are not known. That is, the
process’ type switch
was not
built to recognize the type and/or subtype of the message received.
Action The
process should be re-linked with the appropriate type switch including the type
and subtype that are
printed
as part of this error message. Or, the process sending the offending
type/subtype should be altered
to send
a buffer that the receiver understands.
See Also
tuxtypes(5), ubbconfig(5)
405 ERROR: Received message of unknown
type ’type’
Description
The
process received a message whose type is not known. That is, the process’ type
switch was not built
to
recognize the type of the message received.
Action The
process should be re-linked with the appropriate type switch including the type
that is printed as part
of this
error message. Or, the process sending the offending type should be altered to
send a buffer that
the
receiver understands.
See Also
tuxtypes(5), ubbconfig(5)
409 ERROR: Invalid table entry
information given
Description
While
trying to retrieve the status field entry, the tmid passed in is
invalid.
Action Contact
your BEA TUXEDO system Technical Support.
410 ERROR: [Invalid table entry
information given]
Description
While
trying to retrieve the status field entry, the tmid passed in is
invalid.
Action Contact
your BEA TUXEDO system Technical Support.
411 ERROR: [Invalid table information
given]
Description
While
trying to retrieve the TMPROC information associated with the tmid specified,
the entry is found
to be
invalid.
Action Contact
your BEA TUXEDO system Technical Support.
412 ERROR: [Invalid table information
given]
Description
While
trying to retrieve the TMPROC information associated with the tmid specified,
the entry is found
to be
invalid.
Action Contact
your BEA TUXEDO system Technical Support.
415 ERROR: Invalid transaction creation
Description
While
doing a warm start or load of the transaction log, an attempt to add an entry
to the transaction table
was
invalid.
Action Contact
your BEA TUXEDO system Technical Support.
416 WARN: Invalid state stateval for
group groupname while adding transaction
15
Description
While
adding a transaction to the transaction table during warm start or load of the
transaction log of
decided
transactions, the transaction table entry was found to have a group whose state
indicated that the
transaction
was either normally or heuristically rolled back. The state will be overwritten
and no further
notification
will be given as to the inconsistent state of the global transaction.
Action Since
the transaction will most likely be driven through to completion, the rollback
status indicates that
the
operation done by the rolled back transaction will be inconsistent. For
instance, this could indicate
inconsistent
data in a data base. The action to reconcile this situation is application
specific.
417 ERROR: warmstart found bad log page
entry
Description
While
warm starting the transaction log, an inconsistent entry was found in the
transaction table entry
Action Contact
your BEA TUXEDO system Technical Support.
419 ERROR: Exit failure
Description
This
error occurs when the process is unable to detach from shared memory or a
failure is detected while
trying
to release a request queue.
Action Contact
your BEA TUXEDO system Technical Support.
421 ERROR: Memory allocation failure
Description
A
memory allocation failure occurs while the system is mapping the well known IPC
key to an internal
structure.
Action Remove
processes that may be tying up physical memory, ensure that the application ipc
key is correct,
or
verify that the UNIX sysgen process sizing parameters are correct.
422 ERROR: Cannot find own BB entry
Description
While
attempting to shut down a server, the bulletin board entry for the specified
server cannot be found.
Action Try
shutting the server down again. If this fails, you will have to use the UNIX
system kill(1)
command
to remove the process.
423 ERROR: [Cannot update own queue]
Description
While
trying to update the server table entry, the server’s queue entry cannot be accessed.
Action Contact
your BEA TUXEDO system Technical Support.
424 ERROR: Cannot re-queue msg
Description
During
shutdown of a MSSQ set server, the shutdown message needs to be enqueued for
each server
instance.
The message re-queuing has failed.
Action Contact
your BEA TUXEDO system Technical Support.
425 ERROR: [Service receive: unknown
meta-msg type: 0xmsg_type]
Description
The
meta message header type was of an unknown type.
Action Contact
your BEA TUXEDO system Technical Support.
426 ERROR: [Service receive: cannot
send meta-msg reply]
Description
While
advertising a new service, a reply is expected for the meta-message but fails.
Action Contact
your BEA TUXEDO system Technical Support.
427 ERROR: [Cannot find own BB entry]
Description
During
the shutdown of a server the queue must be drained, and while the queue is
being checked the
getqcnt()
call
fails. This error may occur if the Bulletin Board is not locked or the queue
information
passed
is in error.
Action Contact
your BEA TUXEDO system Technical Support.
428 ERROR: Cannot re-queue msg
Description
While
trying to shut down a server, the sentinel message could not be queued.
Action Try
to shut down the server again. If this fails, contact your BEA TUXEDO system
Technical Support.
429 ERROR: Cannot perform shutdown at
this time
Description
An
attempt is made to shut down a group of TMS processes in an invalid order.
Specifying the TMS
processes
to be shut down by group, lmid, or (S) will order the shutdown sequence
properly.
Action The
TMSs should not be shut down individually (using the -i option). The -g -l -S
flags should be used
instead.
430 ERROR: Application rejects shutdown
request
16
Description
The
application has denied a shutdown request. This error can occur in a variety of
different scenarios.
The
system processes such as (D)BBL, TMS, or BRIDGE may reach a condition in which
they are
unable
to shut down. For example, the BBL cannot process a shutdown request because a
server fails to
disconnect.
Application servers may also reach this condition by returning a "0"
value in the default
shutdown
function, _tmsvrstop(). If
this occurs, contact your BEA TUXEDO system application
administrator.
Action Check
the userlog for other messages to determine the proper action to take. In the above
example of a
system
process (BBL) unable to shut down, the force option (-w) may be used.
See Also
tmshutdown(1)
431 ERROR: Service receive: cannot send
meta-msg reply
Description
While
attempting to reply to a shutdown request, the meta-message send fails.
Action Contact
your BEA TUXEDO system Technical Support.
Description
While
trying to send a meta-message, the request cannot be sent. Possible causes may
be a message type
switch
function failure, an invalid message length, or a low level message send
failure.
Action Check
for a partitioned network or corrupted shared memory. Check that all
administrative processes are
running
and that the sysgen parms (IPC parameters) for messages are appropriate. Also
check the userlog
for
additional messages that may help to isolate the problem. Contact your BEA
TUXEDO system
Technical
Support.
439 ERROR: Migration failed: Not all
the servers are shutdown
Description
While
attempting to migrate servers to another machine, the system is unable to
process this request. All
of the
servers affected by this request must be shut down.
Action Shut
down the desired servers with the relocate (-R) option and reissue the migrate
request.
See Also
BEA TUXEDO Administrator’s Guide,
tmadmin(1)
441 ERROR: Migration failed: alternate
location not specified
Description
When
attempting to migrate server(s) to another site, the system is unable to
complete the request
because
the alternate location is not specified for an affected server group(s).
Action The
LMID entry in the GROUPS section
for the affected server groups must be updated. This may be
achieved
by using the tmconfig() command
and updating the TA_LMID field of the affected server
groups
to include the alternate location.
See Also
BEA TUXEDO Administrator’s Guide,
tmadmin(1), tmconfig(1)
442 ERROR: Migration failed: alternate
locations not the same
Description
When
attempting to migrate server(s) to another site, the system is unable to
complete the request
because
the alternate locations specified for the affected server group(s) are not the
same.
Action The
appropriate action for this request depends on if the alternate locations are
set properly or not. If the
alternate
locations of server groups on an lmid are different, they may be migrated
independently by
group.
See the tmadmin() subcommand
migrategroup.
If the
groups are to be moved to the same lmid, the LMID entry in the GROUPS section for the affected
server
groups must be updated. This may be achieved by using the tmconfig() command and
updating
the TA_LMID field of the affected server groups to specify the same alternate
location. Then
the
request may be resubmitted.
See Also
BEA TUXEDO Administrator’s Guide,
tmadmin(1), tmconfig(1)
445 INFO: BB on machine lmid has
been updated for migration of group group_name.
Description
During
a migration request, this message is issued to point out that the bulletin
board for the alternate
location
(lmid) has been updated.
Action No
action necessary.
446 INFO: BB on machine lmid has
been update for migration of groups from machine lmid.
Description
During
a migration request, this message is issued to point out that the bulletin
board for the alternate
location
(lmid) has been updated.
Action No
action necessary.
459 ERROR: Send to BRIDGE failed
17
Description
While
trying to get the status of a remote queue via tmadmin, the message to the
remote BRIDGE failed.
Action Check
the userlog for earlier messages indicating the cause of the failure.
460 ERROR: Send to BRIDGE failed
Description
While
trying to get the status of a remote queue via tmadmin, the message to the
remote BRIDGE failed.
Action Check
the userlog for earlier messages indicating the cause of the failure.
461 ERROR: Memory allocation failure
Description
An
attempt dynamically to allocate memory from the operating system using malloc() failed while
trying
to suspend the BRIDGE during a partitioned shutdown.
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.
462 ERROR: Retrieved too many entries
in tmsuspend
Description
While
trying to suspend the BRIDGE during a partitioned shutdown, the number of
server entries
retrieved
is larger than the number of entries allocated for retrieval. This should not
occur.
Action Re-run
the tmshutdown command.
See Also
tmshutdown(1)
463 ERROR: TMUSEBRANCH option not supported
Description
When
opening a resource manager with tpopen, the resource manager had the
TMUSEBRANCH flag set
from the
XA Preliminary Specification. This option is not supported.
Action Contact
your resource manager vendor.
466 ERROR: tpopen TPERMERR xa_open
returned errstring
Description
The
call to xa_open from within tpopen returned the XA error value errstring.
Action Check
the error reporting mechanism for the associated resource manager to determine
the cause of the
problem.
Contact your BEA TUXEDO system Technical Support or resource manager vendor.
467 ERROR: tpclose TPERMERR xa_close
returned errstring
Description
The
call to xa_close from within tpclose returned the XA error value errstring.
Action Check
the error reporting mechanism for the associated resource manager to determine
the cause of the
problem.
Contact your BEA TUXEDO system Technical Support or resource manager vendor.
470 ERROR: Memory allocation failure
Description
An
attempt dynamically to allocate memory from the operating system using malloc() failed while
trying
to put variables into the environment for either the machine or server ENVFILE.
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.
474 ERROR: Memory allocation failure
Description
An
attempt dynamically to allocate memory from the operating system using malloc() failed while
receiving
a service request in a server.
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.
476 WARN: Server groupid/serverid:
client process processid: lost message
Description
A
server died and the specified server (with group groupid and server
identifier serverid) is recovering
on its
behalf. A message from the client with the specified processid has been
lost. Additional
information
will be printed in subsequent messages
Action No
action required.
See Also
See
Messages 477 and 478 below.
477 WARN: SERVICE=servicename MSG_ID=msgid
REASON=server died
Description
A
server died (see message 476) while processing service servicename. The
client from which the
message
was sent is still active so a response message will be sent indicating the
failure.
Action No
action required.
478 WARN: SERVICE=servicename MSG_ID=msgid
REASON=server and client died
18
Description
A
server died (see message 476) while processing service servicename. The
client from which the
message
was sent is no longer active either so that a response message cannot be sent
indicating the
failure.
Action No
action required.
Description
When
receiving a service request in a server, the server was unable to find its own
entry in the Bulletin
Board.
Action Check
the userlog for earlier messages indicating problems with the application and
check with the
application
administrator. Contact your BEA TUXEDO system Technical Support.
481 ERROR: Service xa_start returned errno
Description
A
message request was received indicating that the message should be handled by
the server in
transaction
mode and the corresponding xa_start failed. xa_start failed because the return
code was out of
range.
Action Perform
the action appropriate for the indicated error.
482 ERROR: Service request found state state_val
for group grpname
Description
A
message request was received indicating that the current transaction was to be
committed, but the state
of the
transaction was neither active or aborted.
Action Check
for a corrupted GTT in shared memory.
486 ERROR: Service request problem,
tperrno = tperrno_val
Description
A
message request was received indicating that the message should be handled by
the server in
transaction
mode and the corresponding tpbegin failed.
Action Verify
that message was not received by an unsolicited message handler, the server was
not part or
registered
with the application, the global transaction id was valid, the server had no
outstanding reply
messages,
the resource manager was not opened, there was not enough space in the global
transaction
table,
the resource manager xa_start failed, or a BBL lock or unlock failed.
487 ERROR: Cannot call ATMI routine
without joining application
Description
tpreturn
was called and the server was no longer part of the application.
Action Either
a tpsvrinit failed or a tpsvrdone was called before tpreturn.
488 ERROR: Invalid data pointer given
to tpreturn()
Description
tpreturn
was given a pointer to a message that did not contain the appropriate magic
numbers in the
message
header, or the address of the message did not begin on a long word boundary.
Action Check
that the application’s IPCKEY is correct, or two applications are using the
same IPCKEY, or the
message
queue isn’t corrupted, or a previously tpalloc ’ed message was invalidated (via
a tpfree) before
tpreturn
was called.
489 ERROR: Performed tpreturn() with
outstanding replies
Description
A
tpreturn was called with outstanding message replies.
Action Check
the service code and make sure that tpreturn is not called before all the
tpacall and tpgetrply ’s are
complete,
all outstanding messages sent to other services have returned, and/or there are
not two
applications
using the same IPCKEY.
495 ERROR: tpreturn tpcommit reported tperrno_msg
Description
The
service automatically started a transaction. tpreturn performed a tpcommit and
it failed with a
tperrno_val
other
than TPEABORT. The specific error is reported as part of this message.
Action Respond
according to the type of error indicated in the message.
499 ERROR: Invalid table entry
information given
Description
A
table id was passed to the update routine that did not correspond to the
server, queue, or service (the
manner
in which information is arranged in the BB).
Action Check
for corrupted shared memory or an invalid IPCKEY (wrong application).
19
LIBTUX Messages 500-599
500 ERROR: Invalid status given
Description
A
status was passed to the update routine that was neither suspended nor not
suspended.
Action Check
for corrupted shared memory or an invalid IPCKEY (wrong application).
501 ERROR: Memory allocation failure
Description
malloc failed when an attempt was made to
acquire space for a table large enough to hold a long word
entry
for all the services in a server.
Action Check
for corrupted shared memory, inappropriate sysgen memory or process parameters,
or if there are
too many
running processes.
502 ERROR: Memory allocation failure
Description
malloc failed when an attempt was made to
acquire space for a table large enough to hold a long word
entry
for each service in a MSSQ set. A status update was being attempted.
Action Check
for corrupted shared memory, inappropriate sysgen memory or process parameters,
or if there are
too many
running processes.
503 ERROR: Cannot find DBBL
Description
An
attempt was made to send a message to the DBBL, and its whereabouts could not
be ascertained
either
from the BB or from a BRIDGE process.
Action Check
for a partitioned network, corrupted shared memory, or if all administrative
processes are running.
505 ERROR: Send/receive error on remote
procedure call
Description
A
message send failed. The message send failure may have resulted from a message
type switch function
failure,
from an invalid message length, or from a low level message send failure.
Action Check
for a partitioned network, corrupted shared memory, if all the administrative
processes are
running,
or if the sysgen parameters for messages are appropriate.
506 ERROR: Send/receive error on remote
procedure call
Description
Two
attempts were made to send a message to a D(BBL) and both attempts failed.
Either the recipient
was not
active (alive), or the sending of the message send itself failed. The message
send failure may
have
resulted from a message type switch function failure, from an invalid message
length, or from a low
level
message send failure.
Action Check
for a partitioned network, corrupted shared memory, if all the administrative
processes are
running,
or if the sysgen parameters for messages are appropriate.
515 ERROR: Null message buffer, cannot
dispatch service
Description
The
run server function, which continually dequeues messages (service requests),
called the server
dispatch
routine with a null message pointer. This means that the dequeuing of a message
failed.
Action System
message resources may be corrupted.
516 ERROR: Unknown service request name
Description
The
server dispatch function calls a high level service dispatch which attempts to
find the entry point
address
of the service and cannot. The server dispatch function records this error.
Action Shared
memory may be corrupted, or the ipc application key is not correct.
517 ERROR: Failed sending reply
Description
The
server dispatch function calls a high level service dispatch which attempts to
find the entry point
address
of the service and cannot. The server dispatch function conveys this error to
the caller via a
message
(reply). If the message send fails, this message appears.
Action System
message resources may be exhausted, the application may be partitioned, or
shared memory is
corrupted.
518 ERROR: Service ’name’ failed
to call tpreturn or tpforward
20
Description
The
server dispatch function calls the service. Control returning after this call
is an indication that
tpreturn
failed
(it does a longjmp and
should never return after the call), or tpforward
failed
(it
gives up
control to another server). These are the only two ways a service can surrender
control after
processing
a service.
Action The
stack in the service became corrupted. Try running the service under a
debugger.
See Also
tpsvrdone(3c)
521 ERROR: Clients cannot call
tpsvrdone
Description
The
process invoking the default server termination function is a client (should be
a server).
Action The
default server termination library function was linked into a process not
identified in the SERVERS
section
of the configuration file, or shared memory is corrupted.
See Also
tpservice(3c)
522 INFO: Default tpsvrdone() function
used
Description
This
message indicates that the system-provided default server exit routine was used
in stopping the
server.
Action No
action required
See Also
tpservice(3c)
524 ERROR: Only servers allowed to call
tpsvrinit
Description
The
process invoking the default server initialization function is not a TUXEDO
System/T server.
Action The
default server initialization library function was linked into a process not
identified in the SERVERS
section
of the configuration file, or shared memory is corrupted.
See Also
tpservice(3c)
525 INFO: Default tpsvrinit() function
used
Description
This
message indicates that the system-provided default server initialization
routine was used in starting
the
server.
Action No
action required
See Also
tpservice(3c)
530 ERROR: NULL service name, cannot
dispatch service request
Description
The
service start routine, called by the start work routine (which is called by the
service dispatch routine),
failed
because the dispatched message contained no service request name.
Action Verify
that the application ipc key is correct, or that not more than one application
is using the same ipc
key, or
some other failure occurred with the associated message queues.
531 ERROR: Function address set to -1
Description
The
service start routine, called by the start work routine (which is called by the
service dispatch routine),
failed
because the bulletin board entry for the requested service function address
contains a zero.
Action Verify
that the application ipc key is correct, or that not more than one application
is using the same ipc
key.
532 ERROR: Invalid message pointer
given
Description
The
service dispatch routine passed the service start work routine a null pointer
due to a TPESYSTEM
error
that occurred earlier. This occurred in either a (D)BBL or server and indicates
that a corrupt or
invalid
message was received.
Action Verify
that the correct machine types are set, or that the application ipc key is
correct, or that not more
than one
application is using the same ipc key.
533 ERROR: Cannot execute service,
address not known
Description
During
the service dispatch, the service start function returned null indicating a
failure. This could be due
to a
null service name appearing in the dispatched message, or the requested service
cannot be found, or
the
bulletin board could not be locked.
Action Verify
that the application ipc key is correct, or that not more than one application
is using the same ipc
key, or
that the service is advertised.
534 ERROR: Work completed, cannot stop
twice
21
Description
When
a service returns from dispatch, a flag is checked to see if the service was
started successfully. If
this
flag is not set, the above error message appears. This flag is only turned on
if the service starts, and
turned
off only when the service done function completes. Either the service never
started or the service
done
function was called more than once.
Action Check
the ulog for additional information about
server failures.
536 ERROR: Unable to create request
queue
Description
An
internal function used to create a UNIX system message queue for Inter-Process
Communications
failed.
Action Check
with your UNIX System Administrator and increase the appropriate message
parameter for your
system.
The possible parameters that may need to be increased are MSGMAX, MSGMNB,
MSGMNI,
MSGSSZ,
and MSGSEG.
537 ERROR: Unable to create reply queue
Description
An
internal function used to create a UNIX system message queue for Inter-Process
Communications
failed.
Action Check
with your UNIX System Administrator and increase the appropriate message
parameter for your
system.
The possible parameters that may need to be increased are MSGMAX, MSGMNB,
MSGMNI,
MSGSSZ,
and MSGSEG.
See Also
BEA TUXEDO Installation Guide
538 ERROR: Unable to remove request
queue queue_id (errno=err_val)
Description
An
internal function used to remove a UNIX system message queue for Inter-Process Communications
failed.
The UNIX system function msgctl returned
an error.
Action Contact
your UNIX System Administrator.
539 ERROR: Unable to remove reply queue
queue_id (errno=errno_val)
Description
An
internal function used to remove a UNIX System message queue for Inter-Process
Communications
failed.
The UNIX System function msgctl returned
an error.
Action Contact
your UNIX System Administrator.
540 ERROR: TUXCONFIG environment value
(string) does not match configuration file
(string)
Description
The
TUXCONFIG parameter
defined in the TUXEDO System/T configuration file does not match the
current TUXCONFIG shell environment variable.
Action Set
the TUXCONFIG variable
in your current shell to match the value defined in the configuration file
and then
export it. Re-create the binary configuration file by executing tmloadcf and then tmboot.
See Also
tmboot(1), tmloadcf(1),
ubbconfig(5)
541 WARN: Server group_name/server_id
terminated
Description
A
server has died. The BEA TUXEDO system will attempt to clean or restart the
server according to the
specification
of the server in the configuration.
Action No
action required
See Also
ubbconfig(5)
542 WARN: Bulletin Board update error error_val
Description
A
server had died. The BEA TUXEDO system was attempting to clean or restart the
server according to
the
specification of the server in the configuration. The server was either
non-restartable, or the
generation
count was exceeded.
Action Determine
why the server is dying. If required, modify the configuration file to increase
the generation
count
and/or make the server restartable.
See Also
ubbconfig(5)
543 WARN: Bulletin Board update error error_val
Description
A
server had died. The BEA TUXEDO system was attempting to clean or restart the
server according to
the
specification of the server in the configuration. The server was either
non-restartable, or the
generation
count was exceeded.
Action Determine
why the server is dying. If required, modify the configuration file to increase
the generation
count
and/or make the server restartable.
See Also
ubbconfig(5)
544 ERROR: Unable to delete server group_name/server_id
22
Description
A
non-restartable server had died. The BEA TUXEDO system was attempting to clean
up after the
aforementioned
incident, but both the clean-up as well the removal of resources allocated to
the server
failed.
Action Contact
your BEA TUXEDO system Technical Support.
545 ERROR: Unable to update Bulletin
Board, error: error_val
Description
The
BEA TUXEDO system attempted to update the server table that resides in UNIX
System shared
memory.
The update was not successful. Either the server information provided was
invalid, or an
attempted
lock on the TUXEDO System/T bulletin board was unsuccessful.
Action Contact
your BEA TUXEDO system Technical Support
546 ERROR: Unable to update Bulletin
Board, error: error_val
Description
The
BEA TUXEDO system attempted to update the server table that resides in UNIX
System shared
memory.
The update was not successful. Either the server information provided was
invalid, or an
attempted
lock on the TUXEDO System/T bulletin board was unsuccessful.
Action Contact
your BEA TUXEDO system Technical Support
547 ERROR: Unable to clean up BBL
processes
Description
The
BEA TUXEDO system attempted to clean up a system process, an action not
permitted at that point.
Action Contact
your BEA TUXEDO system Technical Support
548 ERROR: Unable to clean up BRIDGE
processes
Description
The
BEA TUXEDO system attempted to clean up a system process, an action not permitted
at that point
Action Contact
your BEA TUXEDO system Technical Support
549 ERROR: Unable to clean up processes
on remote node(s)
Description
The
BEA TUXEDO system attempted to clean up processes that are running on a remote
computer, and
that operation
is not permitted at that point.
Action Contact
your BEA TUXEDO system Technical Support
550 WARN: Cleaning up restartable
server group_name/server_id
Description
The
BEA TUXEDO system is about to clean up a server that was defined to be
restartable.
Action No
action required.
551 WARN: Cleaning up server group_name/server_id
Description
The
TUXEDO System is about to clean up a server table entry.
Action No
action required.
552 WARN: TUXDIR environment variable
not set
Description
The
BEA TUXEDO system environment variable TUXDIR
was
not set.
Action Set
and export the environment variable TUXDIR and
repeat the operation.
See Also
BEA TUXEDO Installation Guide
553 ERROR: Multi-processor operation
sysmulti failed - errno=error_val
Description
The
TUXEDO System/T application was running on a multi-processor environment. While
attempting to
use the sysmulti function, an error was detected.
Action Contact
your UNIX System Administrator.
554 ERROR: Multi-processor operation
sysmulti failed - errno=error_val
Description
The
TUXEDO System/T application was running on a multi-processor environment. While
attempting to
use the sysmulti function, an error was detected.
Action Contact
your UNIX System Administrator.
555 ERROR: Unable to exec command -
errno=errno_val
Description
The
BEA TUXEDO system attempted to execute the cleanupsrv
process.
The UNIX System library
function
system() failed.
Action Contact
your UNIX System Administrator.
556 ERROR: Unable to determine ID of
server to be removed
Description
The
BEA TUXEDO system attempted to remove a server process, but was unable to
determine its ID.
Action Contact
your BEA TUXEDO system Technical Support
23
557 INFO: Server group_name/server_id
being restarted
Description
The
BEA TUXEDO system is restarting a server process.
Action No
action required.
558 ERROR: Restarting a remote server
not permitted
Description
The
application is trying to remote restart a server process. This operation is not
permitted.
Action No
action required
559 ERROR: TUXDIR environment variable
not set for restartsrv process
Description
The
BEA TUXEDO system environment variable, TUXDIR,
is not set. Because of this the
restartsrv
process
cannot be executed.
Action Set
and export the TUXDIR environment
variable and repeat the operation.
561 ERROR: Multi-processor operation
sysmulti failed - errno=errno_val
Description
The
TUXEDO System/T application was running on a multi-processor environment. While
attempting to
use the sysmulti function, an error was detected.
Action Contact
your UNIX System Administrator.
562 ERROR: Multi-processor operation
sysmulti failed - errno=errno_val
Description
The
TUXEDO System/T application was running on a multi-processor environment. While
attempting to
use the sysmulti function, an error was detected.
Action Contact
your UNIX System Administrator.
563 ERROR: Unable to exec command -
errno=errno_val
Description
The
TUXEDO System/T application was running on a multi-processor environment. While
attempting to
use the sysmulti function, an error was detected.
Action Contact
your UNIX System Administrator.
564 ERROR: Unable to exec command application
RCMD command - errno=errno_val
Description
The
BEA TUXEDO system attempted to execute the application-specified RCMD command associated
with the
server to be restarted. The UNIX System library function system() used for this operation
failed.
Action Contact
your UNIX System Administrator.
575 ERROR: Unable to reset semaphore
for sem key_val, errno errno_val
Description
The
BEA TUXEDO system was in the process of cleaning up a registry slot for a
process. While doing
the
aforementioned operation, the semaphore used for that process had to be reset.
The semaphore
operation
semctl failed.
Action Contact
your BEA TUXEDO system Technical Support
576 ERROR: Unable to remove queue for
process pid
Description
The
BEA TUXEDO system was in the process of cleaning up a registry slot for a
process. A part of this
clean up
involves removing queues used by that process. The operation used to remove the
queue failed.
Action Contact
your BEA TUXEDO system Technical Support
577 ERROR: Unable to register because
the slot is already owned by another process
Description
While
registering a process, a conflict arose with regard to a slot in the registry
table. Another process
already
owned that slot.
Action Contact
your BEA TUXEDO system Technical Support
578 ERROR: Unable to register because
the slot is already owned by another process
Description
While
registering a process, a conflict arose with regard to a slot in the registry
table. Another process
already
owned that slot.
Action Contact
your BEA TUXEDO system Technical Support
579 ERROR: Unable to obtain the
registry slot owned by process
Description
The
BEA TUXEDO system was attempting to restart a server. In so doing, the system
was unable to
determine
the registry table slot that was originally used by the restarting process.
Action Contact
your BEA TUXEDO system Technical Support
580 ERROR: Attempt to take over
registry table entry of non-restarting process
24
Description
The
BEA TUXEDO system attempted to use a registry table slot in a manner that is
not permitted.
Re-using
a registry table slot is permitted for servers that are restarting, but not for
a server that is defined
to be
non-restartable.
Action Contact
your BEA TUXEDO system Technical Support
581 ERROR: Migrating and given an old
pid when none expected
Description
The
BEA TUXEDO system was attempting to find a registry table slot for a restarting
server, but the
server
was set up to migrate.
Action Contact
your BEA TUXEDO system Technical Support
582 ERROR: Unable to register, registry
table full
Description
The
BEA TUXEDO system was attempting to find a registry table slot for a process,
but the registry
table
was full.
Action Increase
the MAXACCESSERS parameter
in the UBBCONFIG file,
rebuild the TUXCONFIG file,
then
reboot
the application and try again.
See Also
ubbconfig(5), tmboot(1)
583 ERROR: Not a privileged user,
incorrect permissions
Description
The
user attempted to execute TUXEDO System/T functions that are reserved for users
with the correct
permissions,
but was not authorized to do so.
Action Contact
your BEA TUXEDO system Technical Support
See Also
ubbconfig(5), tmadmin(1)
584 ERROR: Invalid registry table slot
index passed, unable to register
Description
When
a process attempts to register with the BEA TUXEDO system, the administrative
process(es)
supplied
update the internal registry table. In this instance, the registry table index
to be used exceeded
the
number of MAXACCESSERS specified
in the configuration file.
Action Increase
the value of the MAXACCESSERS parameter
in the UBBCONFIG file,
rebuild the TUXCONFIG
file,
reboot the TUXEDO System/T application, and repeat the operation(s).
See Also
ubbconfig(5)
585 ERROR: Invalid registry table slot
index passed, unable to unregister
Description
The
BEA TUXEDO system administrative process attempted to unregister a process, but
failed in doing
so
because the index into the registry table to be used was outside the bounds of
the registry table.
Action Contact
your BEA TUXEDO system Technical Support
586 ERROR: Unable to unregister process
pid - errno errno_val tperrno tperror_val
Description
The
BEA TUXEDO system administrative process attempted to unregister a process, but
failed.
Action Contact
your BEA TUXEDO system Technical Support
587 INFO: Process pid that is
unregistering has ticket ticket
Description
The
process that is unregistering from the TUXEDO System/T application is holding a
ticket for the
user-level
semaphore. The ticket value will be cleared as part of the unregistration.
Action No
action required.
588 ERROR: Unable to open TUXCONFIG
file
Description
The
TUXEDO System/T administrative process was unable to open the TUXCONFIG file.
Action Contact
your BEA TUXEDO system Technical Support
589 ERROR: Unable to read the
*RESOURCES section of the TUXCONFIG file
Description
The
TUXEDO System/T administrative process was unable to read the RESOURCES section of the
TUXCONFIG
file.
Action Contact
your BEA TUXEDO system Technical Support
590 ERROR: Unable to read the TUXCONFIG
file, version type mismatch
Description
The
TUXEDO System/T administrative process was unable to read the TUXCONFIG file because of a
mismatch
of version types.
Action Contact
your BEA TUXEDO system Technical Support
591 ERROR: Unable to read the TUXCONFIG
file, release mismatch
25
Description
The
TUXEDO System/T administrative process was unable to read the TUXCONFIG file because the
BEA
TUXEDO system release number stored in the TUXCONFIG
file
did not match the release number
compiled
into the system.
Action Contact
your BEA TUXEDO system Technical Support
592 ERROR: Invalid model stored in the
TUXCONFIG file, must be SHM or MP
Description
The
MODEL parameter value stored in the TUXCONFIG file was not MP
or
SHM.
Action Check
the configuration file and ensure that the MODEL
parameter
value in the RESOURCES section
is
MP
or
SHM.
See Also
ubbconfig(5)
593 ERROR: Unable to map ID of a PE to
ipckey
Description
The
BEA TUXEDO system was unable to determine the PE and IPCKEY mapping for a
particular PE
Action Contact
your BEA TUXEDO system Technical Support
594 ERROR: Unable to locate PE entry in
the Bulletin Board
Description
The
BEA TUXEDO system was unable to locate information for a PE in the Bulletin
Board.
Action Contact
your BEA TUXEDO system Technical Support
595 ERROR: No ’string’ entry in table_name
table
Description
The
BEA TUXEDO system was unable to locate information for the specified string in
the Bulletin
Board
table specified. It may be that the server was built with an inappropriate
"-b {shm|mp}"
option;
for
example, a server built with "-b shm"
will produce the message:
No
’MP’ entry in model table.
when
booted in a MP application.
Action Contact
your BEA TUXEDO system Technical Support
See Also
buildserver(1)
596 ERROR: [NULL service name used to
get service information]
Description
A
BEA TUXEDO system internal function was used to retrieve service information
from the services
table,
but a NULL service name was used.
Action Contact
your BEA TUXEDO system Technical Support
597 ERROR: [Unable to open the
*SERVICES section table]
Description
A
BEA TUXEDO system internal function was used to retrieve service information
from the services
table,
but the open failed.
Action Contact
your BEA TUXEDO system Technical Support.
598 ERROR: [Unable to read information
from the *SERVICES section table]
Description
A
BEA TUXEDO system internal function was used to retrieve service information
from the services
table,
but the open failed.
Action Contact
your BEA TUXEDO system Technical Support.
599 ERROR: Maximum number of types/subtypes,
number, has been exceeded
Description
The
maximum number of types/subtypes permitted for a particular TUXEDO System/T
service has been
exceeded.
Action Review
the configuration file, verify that all services use less than the maximum
number of
types/subtypes,
and rebuild the TUXCONFIG file.
See Also
ubbconfig(5), tmloadcf(1)
26
LIBTUX Messages 600-699
600 ERROR: [Invalid buffer type
information type]
Description
The
buffer type information provided in the configuration file was incorrect.
Action Check
the configuration file, verify that the buffer type provided is correct, and
repeat the operation.
See Also
ubbconfig(5), tmloadcf(1)
601 ERROR: [Invalid buffer subtype
information subtype_val]
Description
The
buffer subtype information provided in the configuration file was incorrect.
Action Check
the configuration file, verify that the buffer type provided is correct, and
repeat the operation.
See Also
ubbconfig(5), tmloadcf(1)
602 ERROR: TUXCONFIG environment
variable not set
Description
The
TUXCONFIG environment variable is not set.
Action Set
and export the TUXCONFIG environment variable, which should be the same as
defined in the
UBBCONFIG
file.
See Also
ubbconfig(5)
603 ERROR: TUXCONFIG file filename does
not exist
Description
The
TUXCONFIG file, filename, does not exist.
Action 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.
See Also
tmloadcf(1), ubbconfig(5)
604 ERROR: Cannot get file status on
TUXCONFIG file filename, errno = errno_val
Description
Cannot
get the file status on the TUXCONFIG file, filename.
Action Check
the UNIX errno for reasons and take appropriate actions accordingly.
See Also
stats(2) in UNIX system reference
manuals
605 ERROR: TUXOFFSET environment
variable must be >= 0
Description
The
TUXOFFSET environment variable is less than 0.
Action 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.
See Also
ubbconfig(5)
607 ERROR: Cannot open section section_name
of the TUXCONFIG: file
Description
The
section_name of the TUXCONFIG file cannot be opened. The TUXCONFIG file
might be
corrupted.
Action You
can shut down the application and re-load the TUXCONFIG file using tmloadcf. If
the error still
occurs,
contact your BEA TUXEDO system Technical Support.
See Also
tmloadcf(1)
608 ERROR: Memory allocation failure
Description
Memory
allocation failed for adding new sections in the TUXCONFIG file.
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.
610 ERROR: Cannot close the TUXCONFIG
file
Description
The
TUXCONFIG file in the VTOC table cannot be closed.
Action Check
the permission and the existence of the TUXCONFIG file, or contact your BEA
TUXEDO system
Technical
Support.
612 ERROR: Read an entry from the VTOC
table failed
27
Description
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
3. the
table itself got corrupted which caused read()
to
fail.
Action Check
your disk tables such as VTOC for possible corruptions and/or damages. If this
error still occurs,
contact
your BEA TUXEDO system Technical Support.
See Also
read(2) in UNIX system reference
manuals
614 ERROR: Cannot write to the section_name
of the TUXCONFIG file which is not opened
Description
Cannot
write to the section_name of the TUXCONFIG file which was never opened.
Action Check
your TUXCONFIG file, or contact your BEA TUXEDO system Technical Support.
See Also
tmunloadcf(1), write(2) in UNIX system reference manuals
615 ERROR: Write to the section_name
of the TUXCONFIG file failed
Description
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
3. the
table itself got corrupted which caused write()
to
fail.
Action Check
your disk tables such as VTOC for possible corruptions and/or damages. If this
error still occurs,
contact
your BEA TUXEDO system Technical Support.
See Also
write(2) in UNIX system reference
manuals
616 ERROR: The routing section of the
TUXCONFIG file cannot be located
Description
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
3. the
TUXOFFSET environment variable was less than zero.
Action Contact
your BEA TUXEDO system Technical Support. See Messages 602, 605, and 607 in
this chapter
for
explanation.
624 ERROR: Data tables for routing
section full
Description
Data
routing tables in the Bulletin Board are full when parsing the routing range
and creating the data
routing
entries.
Action This
is a system error, contact your BEA TUXEDO system Technical Support.
625 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 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).
See Also
ubbconfig(5)
626 ERROR: Range values out of order upper_range
< lower_range
Description
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.
Action 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.
See Also
ubbconfig(5)
627 ERROR: More than one wild card in
entry range
28
Description
More
than one wild-card (*) range for the integer routing data was specified in the
data routing entry.
Action 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).
See Also
ubbconfig(5)
628 ERROR: Range values out of order upper_range
< lower_range
Description
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.
Action 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.
See Also
ubbconfig(5)
629 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 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).
See Also
ubbconfig(5)
630 ERROR: Range values out of order upper_range
< lower_range
Description
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.
Action 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.
See Also
ubbconfig(5)
631 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 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).
See Also
ubbconfig(5)
ERROR: Range values out of order upper_range
< lower_range
Description
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.
Action 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.
See Also
ubbconfig(5)
633 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 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).
See Also
ubbconfig(5)
634 ERROR: Range values out of order upper_range
< lower_range
Description
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.
Action 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.
See Also
ubbconfig(5)
635 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 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).
See Also
ubbconfig(5)
29
636 ERROR: Range values out of order upper_range
< lower_range
Description
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.
Action 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.
See Also
ubbconfig(5)
637 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 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).
See Also
ubbconfig(5)
638 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 value is less than the
lower
range value.
Action 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.
See Also
ubbconfig(5)
639 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 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).
See Also
ubbconfig(5)
640 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
value is less than the
lower
range value.
Action 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.
See Also
ubbconfig(5)
641 ERROR: Unknown field type was
specified for data routing entry
Description
An
unknown field type was specified in the data routing entry.
Action Check
the field types specified in the ROUTING section of the UBBCONFIG file.
See Also
ubbconfig(5)
642 ERROR: Expected colon to separate
server group range
Description
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.
Action 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.
See Also
ubbconfig(5)
643 ERROR: Expected comma after group
name grpname,string
Description
Within
a range and a server group pair, a comma (,) is expected after server group
name in the
ROUTING
section of the UBBCONFIG file.
Action Check
the range and the server group specified in the ROUTING section of the
UBBCONFIG file. A
comma
(,) is expected after the server group name.
See Also
ubbconfig(5)
644 ERROR: Expecting keyword MAX
30
Description
The
keyword MAX is expected to indicate the maximum value for the data type of the
associated field in
the
ROUTING section of the UBBCONFIG file.
Action Check
the range and server group specified in the ROUTING section of the UBBCONFIG
file. The
keyword
MAX should be specified to indicate the maximum value for the data type of the
associated
field.
See Also
ubbconfig(5)
645 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
ROUTING section of the UBBCONFIG file.
Action Check
the range and the server group specified in the ROUTING section of the
UBBCONFIG file. The
keyword
MIN should be specified to indicate the minimum value for the data type of the
associated field.
See Also
ubbconfig(5)
646 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 ROUTING section of the UBBCONFIG file.
Action Check
the range and server group specified in the ROUTING section of the UBBCONFIG
file. The
keyword
MAX or MIN should be specified to indicate the maximum or the minimum value for
the data
type of
the associated field.
See Also
ubbconfig(5)
647 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 ROUTING section of the
UBBCONFIG file.
See Also
ubbconfig(5)
648 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 ROUTING section of the
UBBCONFIG
file.
See Also
ubbconfig(5)
649 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 ROUTING section of the
UBBCONFIG file.
See Also
ubbconfig(5)
650 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 ROUTING section of the
UBBCONFIG
file.
See Also
ubbconfig(5)
651 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 ROUTING section of the
UBBCONFIG file.
See Also
ubbconfig(5)
652 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 ROUTING section of the
UBBCONFIG
file.
See Also
ubbconfig(5)
653 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 ROUTING section of the
UBBCONFIG file.
A char
routing data must be begun with a single quote (’).
See Also
ubbconfig(5)
654 ERROR: Expected single quote to end
char routing data value
31
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 ROUTING section of the
UBBCONFIG file.
A char
routing data must be ended with a single quote (’).
See Also
ubbconfig(5)
655 ERROR: No more string pool free
space available for routing strings and carrays
Description
The
routing string pool in the Bulletin Board is full when filling the data routing
section with string and
carray
data.
Action This
is a system error, contact your BEA TUXEDO system Technical Support.
656 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 string and carray routing data in the ROUTING section
of the
UBBCONFIG
file. The string and carray routing data must be within single quotes (’).
See Also
ubbconfig(5)
657 ERROR: No more string pool free
space available for routing strings and carrays
Description
There
is not enough routing free string pool space in the Bulletin Board when filling
the data section with
string
and carray data.
Action This
is a system error, contact your BEA TUXEDO system Technical Support.
659 ERROR: Discovered a 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 ROUTING section of the
UBBCONFIG file. A
string
value is terminated with a NULL character.
See Also
ubbconfig(5)
660 ERROR: [Unable to find server group
section of TUXCONFIG file]
Description
A
BEA TUXEDO system internal function was used to retrieve server group
information from the
TUXCONFIG
file, but the function failed.
Action Contact
your BEA TUXEDO system Technical Support for assistance.
661 ERROR: Invalid logical machine name
- lmid
Description
The
logical machine name identifier provided is invalid. The most likely reason for
that is a duplicate
logical
machine identifier.
Action Check
the configuration file and ensure that no duplicate logical machine names are
being used. If so,
correct
the name and try the operation again.
See Also
ubbconfig(5), tmloadcf(1)
662 ERROR: Invalid logical machine name
- lmid
Description
The
logical machine name identifier provided is invalid. The most likely reason for
that is a duplicate
logical
machine identifier.
Action Check
the configuration file and ensure that no duplicate logical machine names are
being used. If
duplicates
are present, correct the name and try the operation again.
See Also
ubbconfig(5), tmloadcf(1)
663 ERROR: Invalid logical machine name
for server group
Description
The
logical machine name identifier provided for the server group is invalid.
Action Check
the configuration file and ensure that the LMID used for the server group is
correct. Then try the
operation
again.
See Also
ubbconfig(5), tmloadcf(1)
664 ERROR: Duplicate server group entry
Description
A
duplicate entry for server groups was defined.
Action Check
the configuration file and ensure that the server group names and IDs are
unique. Then try the
operation
again.
See Also
ubbconfig(5), tmloadcf(1)
665 ERROR: Invalid server group name - svrgrp_name
Description
Cannot
retrieve server group from the Bulletin Board because an invalid server group
name was given.
Action This
is a system error, contact your BEA TUXEDO system Technical Support.
32
666 ERROR: Message operation failed
because the queue was removed
Description
msgsnd
to a queue failed because the queue was removed.
Action Check
the message queues, or contact your BEA TUXEDO system Technical Support.
See Also
intro(2), msgsnd(2),
msgrcv(2), msgctl(2)
in UNIX system reference manuals
667 ERROR: Message operation failed
because of the bad message type
Description
msgsnd
to a queue failed because of the bad message type.
Action Check
the message type in msgsnd().
The message is probably corrupted. Contact your BEA
TUXEDO
system Technical Support.
See Also
intro(2), msgsnd(2),
msgrcv(2), msgctl(2)
in UNIX system reference manuals
668 ERROR: Message operation failed
because the message size < 0
Description
msgsnd
to a queue failed because the message size is less than zero.
Action Check
the message size in msgsnd().
The message is probably corrupted. Contact your BEA
TUXEDO
system Technical Support.
See Also
intro(2), msgsnd(2),
msgrcv(2), msgctl(2)
in UNIX system reference manuals
669 ERROR: Message operation failed
because of the invalid message queue identifier
Description
msgsnd
to a queue failed because of invalid message queue identifier. This can also
occur if a request is
made by
a client who exits before the request is satisfied. The cleanup after the
client exits removes the
message
queue.
Action Check
the message queue identifier in msgsnd().
The message may be corrupted. Contact your BEA
TUXEDO
system Technical Support.
See Also
intro(2), msgsnd(2),
msgrcv(2), msgctl(2)
in UNIX system reference manuals
670 ERROR: Message operation failed
because the message is too big
Description
msgsnd
to a queue failed because the message is too big.
Action Check
the size of the message in msgsnd().
See Also
intro(2), msgsnd(2),
msgrcv(2), msgctl(2)
in UNIX system reference manuals
671 ERROR: Message operation failed
because the message queue is empty
Description
msgsnd
to a queue failed because the message queue is empty.
Action Check
the message queues.
See Also
intro(2), msgsnd(2),
msgrcv(2), msgctl(2)
in UNIX system reference manuals
672 ERROR: Message operation failed
because the message queue or the system is full
Description
msgsnd
to a queue failed because the message queue or the system is full.
Action Check
kernel parameters for message queues. Re-configure your system to meet your
needs.
See Also
intro(2), msgsnd(2),
msgrcv(2), msgctl(2)
in UNIX system reference manuals
673 ERROR: Message operation failed
because the access permissions were denied
Description
msgsnd
to a queue failed because the message queue cannot be accessed.
Action Check
the message queue permissions.
See Also
intro(2), msgsnd(2),
msgrcv(2), msgctl(2)
in UNIX system reference manuals
674 ERROR: Message operation failed
because of a bad address
Description
msgsnd
to a queue failed because the message pointer is pointing to an illegal
address.
Action Check
the address of the message queue pointer, or contact your BEA TUXEDO system
Technical
Support.
See Also
intro(2),
msgsnd(2), msgrcv(2), msgctl(2) in UNIX system reference manuals
675 ERROR: Message operation failed due
to unknown causes
Description
msgsnd
to a queue failed due to unknown causes.
Action Contact
your BEA TUXEDO system Technical Support.
See Also
intro(2), msgsnd(2),
msgrcv(2), msgctl(2)
in UNIX system reference manuals
678 ERROR: Message send/receive failure
for remote procedure call
33
Description
msgsnd/rcv
failed for remote procedure call requests that are sent to the DBBL (or BBL in
SHM mode).
Possible
causes:
1.
cannot find DBBL
2. a
server died
3.
messages send/receive failed.
Action Check
DBBL, servers, and message queues, or contact your BEA TUXEDO system Technical
Support.
See
Messages 503, 505, and 506 in this chapter for explanation
See Also
intro(2), msgsnd(2),
msgrcv(2), msgctl(2)
in UNIX system reference manuals
679 ERROR: Memory allocation failure
Description
An
attempt dynamically to allocate memory from the operating system using malloc() failed while
making a
private copy of the bulletin board.
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.
680 ERROR: Effective UID or GID does
not match bulletin board
Description
The
calling process’s effective user-id, UID, or group-id, GID, is incorrect. They
should match the UID
and GID
specified in the RESOURCES or *MACHINES section of the configuration file.
Action Run
the process with the correct effective UID and GID.
681 ERROR: Failure to create message queue
Description
A
UNIX system message queue could not be created during BEA TUXEDO system process
initialization.
Action Verify
the UNIX’s kernel parameters related to message queues, and increase if
necessary. In particular,
check
MSGMNI. The BEA TUXEDO system’s multi-server single queue, MSSG, feature allows
multiple
servers to share the same queue, reducing the number required.
See Also
BEA TUXEDO Installation Guide
682 ERROR: Send/receive error for
remote procedure call
Description
A
message send failed. The message send failure may have resulted from a message
type switch function
failure,
an invalid message length, or a low level message send failure.
Action Check
for a partitioned network, corrupted shared memory, all administrative
processes are running, and
sysgen
parms for messages are appropriate.
ERROR: Memory allocation failure
Description
An
attempt dynamically to allocate memory from the operating system using malloc() failed while
creating
a system message buffer.
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.
684 ERROR: Memory allocation failure
Description
An
attempt dynamically to allocate memory from the operating system using malloc() failed while a
server
process was trying to advertise its services.
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.
687 ERROR: Received message with an
unknown release number X
34
Description
A
BEA TUXEDO system message was received with an unknown release number in its
message header.
Messages
from both the current release and the previous release are understood. This
does not include
minor
"point" maintenance releases. For example, a 4.2.1 BEA TUXEDO system
process understands
4.2.1,
4.2, and 4.1 message formats. It does not understand a release 4.0 message,
since that is two major
releases
old.
There is
a different problem if the unknown release number is 0 or a very large number.
It has been
observed
that if the underlying TCP/IP network is unreliable, and drops bytes from the
middle of
messages,
this "unknown release number" error may occur frequently. It would
typically be reported by
the
BRIDGE or WSH process. The problem is that the BEA TUXEDO system message header
describes
how many
bytes follow the header. If some are lost by the network, all subsequent
message headers will
not be
in the correct position in the data stream.
Action Upgrade
any machines in the network running an old release of the BEA TUXEDO system.
Note that the
MASTER
and BACKUP must be upgraded first, so they are always running the most recent
version.
Investigate
and resolve any networking problems. TCP/IP should guarantee reliable
end-to-end transport
of data.
689 ERROR: Received a message that is
smaller than system minimum
Description
A
BEA TUXEDO system message was received by the process, and is known to be
invalid because it
was too
small.
Action A
likely cause is a compressed message being received by a process linked with
release 4.2 or earlier
BEA
TUXEDO system libraries. The message compression feature was introduced in
release 4.2.1, and
should
not be enabled until the entire application is running 4.2.1 or a later
release. This includes
application
client and server processes, which need to be relinked.
695 ERROR: Unknown table type given
Description
An
internal BEA TUXEDO system table was requested, and could not be read because
its type is
unknown.
Action Contact
your BEA TUXEDO system Technical Support.
696 ERROR: Missing search key
Description
An
internal BEA TUXEDO system table was requested, and could not be read because a
search key was
not
provided to the low-level access routine.
Action Contact
your BEA TUXEDO system
Technical Support.
697 ERROR: Missing search key
Description
An
internal BEA TUXEDO system table was requested, and could not be read because a
search key was
not
provided to the low-level access routine.
Action Contact
your BEA TUXEDO system Technical Support.
698 ERROR: Invalid search key
Description
An
internal BEA TUXEDO system table was requested, and could not be read because
an invalid search
key was
passed to the low-level access routine.
Action Contact
your BEA TUXEDO system Technical Support.
699 ERROR: Missing search key
Description
An
internal BEA TUXEDO system table was requested, and could not be read because a
search key was
not
provided to the low-level access routine.
Action Contact
your BEA TUXEDO system Technical Support.
