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.
Contact your TUXEDO System Technical Support.
An attempt to free space that was allocated in the
VTOC
has failed
because there are no more available
VTOC
map entries.
Contact your TUXEDO System Technical Support.
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.
Contact your TUXEDO System Technical Support.
An error occurred because the indicated function was invoked with
invalid arguments.
Contact your TUXEDO System Technical Support.
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 .
Contact your TUXEDO System Technical Support.
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.
Contact your TUXEDO System Technical Support.
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.
Contact your TUXEDO System Technical Support.
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.
Contact your TUXEDO System Technical Support.
An error has occurred because within the function
_gp_vtoc_lock(),
an attempt to obtain a lock on the
VTOC
has failed.
Contact your TUXEDO System Technical Support.
An error has occurred during an access of the
VTOC
and has
resulted in the indicated unrecognizable error code being
returned.
Contact your TUXEDO System Technical Support.
An attempt to locate and write to a free block in the transaction
log has failed.
Retry the operation and if the problem persists, contact
your TUXEDO System Technical Support.
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.
Retry the operation and if the problem persists, contact
your TUXEDO System Technical Support.
An attempt to warmstart has failed because only the
BBL
is allowed
to initiate warmstarts.
Contact your TUXEDO System Technical Support.
The indicated page was skipped while doing a warmstart because
the checksum did not match.
No action required.
The format of the transaction log is unrecognizable.
The release of the software is different than the release of the
transaction log.
Contact your TUXEDO System Technical Support.
An attempt to create the transaction log has failed because a
transaction log already exists.
If a transaction log exists, remove it and retry the desired operation.
If the problem persists, contact your TUXEDO System Technical Support.
A call to internal function
_tlog_start ()
has failed because the caller is neither the
BBL
nor the
TMS .
Contact your TUXEDO System Technical Support.
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.
Check and ensure the accuracy of the
TUXCONFIG
file, and if the problem
persists,
contact your TUXEDO System Technical Support.
An error occurred attempting to open the transaction log with read
and write access.
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 TUXEDO System Technical Support.
An error has occurred opening the transaction log because the
actual size of the
TLOG
differs from the size maintained by the
BB .
Retry the desired operation, and if the problem persists,
contact your TUXEDO System Technical Support.
An attempt dynamically to allocate memory from the operating system
using
malloc ()
has failed within
tpacall ().
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.
tpcall(3)
The presend routine which performs some preliminary checking
on the message before it is encoded and sent has failed; therefore
the message will not be sent.
Make sure the messages you are attempting to send have the
length and pointer fields set correctly.
If the problem persists, contact your TUXEDO System Technical Support.
An attempt to send a message that has a data length of 0 has failed.
Make sure the messages you are attempting to send have the
length and pointer fields set correctly.
If the problem persists, contact your TUXEDO System Technical Support.
An attempt to encode the header of the message has failed, therefore
the message has not been sent.
Make sure the messages you are attempting to send have the
message header length and pointer fields set correctly.
If the problem persists, contact your TUXEDO System Technical Support.
An attempt to encode the data of the message has failed, therefore
the message has not been sent.
Make sure the messages you are attempting to send have the
message data length and location fields set correctly.
If the problem persists, contact your TUXEDO System Technical Support.
An internal function has failed because it attempted to access an
invalid table.
Contact your TUXEDO System Technical Support.
An attempt to allocate a free entry in the Bulletin Board
for tablename has failed
because it is full.
Re-configure the application to increase the size of the associated table.
An attempt to free a registry table entry has failed because the table entry
has not yet been allocated.
Contact your TUXEDO System Technical Support.
An internal function has failed because it attempted to access an
invalid table.
Contact your TUXEDO System Technical Support.
There are no more free entries in the registry table, so an
attempt to allocate an entry has failed.
Contact your TUXEDO System Technical Support.
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.
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.
ulimit(2)
in UNIX system reference manuals
A program was booted in an MP configuration without the Bulletin Board
existing.
Clean up any IPC resources and re-boot the application from scratch.
tmboot(1)
A program was booted without the Bulletin Board
existing.
Clean up any IPC resources and re-boot the application from scratch.
tmboot(1)
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).
Edit the
UBBCONFIG
configuration file,
change the IPCKEY to a unique value, reload the
TUXCONFIG
using
tmloadcf ,
and reboot the application.
tmloadcf (1),
ubbconfig (5)
While initializing the application, a system semaphore could not be created.
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.
While initializing the application, the status of a system semaphore
could not be obtained.
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.
While initializing the application, a program found the TUXEDO
system semaphore existed but was not initialized within 10 seconds.
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.
While initializing the application, a program found the TUXEDO
system semaphore existed but was not initialized within 10 seconds.
This is related to message 338.
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.
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).
Edit the
UBBCONFIG
configuration file,
change the IPCKEY to a unique value, reload the
TUXCONFIG
using
tmloadcf ,
and reboot the application.
tmloadcf (1),
ubbconfig (5)
While initializing the TUXEDO application, shared memory could not
be allocated for the Bulletin Board.
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.
300 ERROR: funcname: UNIX sys call error - errno_val
DESCRIPTION
ACTION
301 ERROR: funcname: cannot free space
DESCRIPTION
ACTION
302 ERROR: funcname: bad table name specified
DESCRIPTION
ACTION
303 ERROR: funcname: invalid arguments or request to function
DESCRIPTION
ACTION
304 ERROR: funcname: bad device name or index specified
DESCRIPTION
ACTION
305 ERROR: funcname: attempt to create overlapping devices
DESCRIPTION
ACTION
306 ERROR: funcname: no entry remains to create device or table or open table
DESCRIPTION
ACTION
308 ERROR: funcname: bad device type (not character special or regular)
DESCRIPTION
ACTION
309 ERROR: funcname: cannot obtain lock on VTOC
DESCRIPTION
ACTION
310 ERROR: errcode: unknown vtoc error code
DESCRIPTION
ACTION
311 ERROR: Cannot locate free block in tlog
DESCRIPTION
ACTION
312 ERROR: Transaction log wrong page number
DESCRIPTION
ACTION
313 ERROR: Log warmstart can only be called by BBL
DESCRIPTION
ACTION
314 INFO: Page page skipped, chksum didn't match
DESCRIPTION
ACTION
315 ERROR: TLOG not in an understandable format. Different release
DESCRIPTION
ACTION
316 ERROR: Transaction log file exists
DESCRIPTION
ACTION
317 ERROR: Log start can only be called by BBL or TMS
DESCRIPTION
ACTION
318 ERROR: Log start cannot get tlog information
DESCRIPTION
ACTION
319 ERROR: Log start cannot open tlog
DESCRIPTION
ACTION
320 ERROR: BB TLOGSIZE differs from number of pages in TLOG file
DESCRIPTION
ACTION
321 ERROR: Memory allocation failure
DESCRIPTION
ACTION
SEE ALSO
322 ERROR: Message presend routine failed
DESCRIPTION
ACTION
323 ERROR: Invalid data length of 0, data not self describing
DESCRIPTION
ACTION
324 ERROR: Encoding of message header failed
DESCRIPTION
ACTION
325 ERROR: Encoding of message data failed
DESCRIPTION
ACTION
327 ERROR: Invalid table type desired
DESCRIPTION
ACTION
328 ERROR: No space in Bulletin Board for tablename
DESCRIPTION
ACTION
329 ERROR: Tried to free non-alloced tmrte
DESCRIPTION
ACTION
330 ERROR: Invalid table type given
DESCRIPTION
ACTION
331 ERROR: No registry table entries
DESCRIPTION
ACTION
332 ERROR: Memory allocation failure
DESCRIPTION
ACTION
SEE ALSO
333 ERROR: No DBBL
DESCRIPTION
ACTION
SEE ALSO
334 ERROR: No BBL
DESCRIPTION
ACTION
SEE ALSO
335 ERROR: Wrong bulletin board type or IPCKEY not unique
DESCRIPTION
ACTION
SEE ALSO
336 ERROR: semget err: errno=errno_val, key = key_val
DESCRIPTION
ACTION
337 ERROR: semctl err: errno=errno_val, key=key_val, id=id_val
DESCRIPTION
ACTION
338 ERROR: BB semaphore not initialized within 10 seconds (key=0xkey_val).
DESCRIPTION
ACTION
339 ERROR: Creating process may be dead; manual intervention required.
DESCRIPTION
ACTION
340 ERROR: Wrong configuration file
DESCRIPTION
ACTION
SEE ALSO
341 ERROR: Could not allocate bulletin board shared memory
DESCRIPTION
ACTION