While compiling a regular expression, an internal error occurred. The message is printed to the standard error and the program is exited with abort ().
Contact your BEA TUXEDO System Technical Support.
rex(1)
When executing rex , a bad command line option flag was specified on the command line.
Re-execute the command with the correct command line options and arguments.
rex(1)
When executing rex to test a regular expression against the data in one or more files, the specified file, filename, could not be opened for reading.
Check that the file exists and has read permission, and re-execute the command.
rex(1)
When executing rex to compile a regular expression from the pattern file, the result of concatenating multiple regular expression patterns was too long (greater than 512 characters).
Modify the pattern file to shorten the regular expression patterns, and re-execute the command.
rex(1)
When executing rex to compile a regular expression from the pattern file, the regular expression pattern name was not found on an input line. Input lines must consist of optional white space followed by a name and double-quoted pattern, separated by white space. The name must begin with an alphabetic or underscore character and contain alphanumeric or underscore characters, and may be up to 30 characters in length.
Correct the pattern file and re-execute the command.
rex(1)
When executing rex to compile a regular expression from the pattern file, a regular expression pattern was too long (longer than 512 characters).
Correct the pattern file and re-execute the command.
rex(1)
The program failed to create and/or open the userlog file filename for writing in append mode. This message will be written to the standard error output of the program.
Check that the directory for the specified filename exists and has write permission, and if the file exists, that it also has write permission.
userlog(3c)
The program failed to write a message to the userlog file filename, with the error value set to errno. This message will be written to the standard error output of the program.
Normally, this indicates that the file system in which the file exists is full; in this case, free up space in the file system and subsequent userlog messages will succeed.
userlog(3c)
The program failed to reset the prefix for the userlog file because dynamic space allocation failed. The userlog file prefix is not reset, and this message will be written to the userlog using the current prefix value.
No action required.
userlog(3c)
While trying to lock a TUXEDO System/T file system for exclusive access, it was discovered that another process had locked the file system and died while holding the lock. The lock is removed and processing continues.
No action required.
While trying to lock a TUXEDO System/T file system for exclusive access, it was discovered that another process is holding the lock.
Use the process identifier, pid, that is printed in the message to determine the process and user running the process, using the ps command. After that process has completed, re-execute the command that failed waiting for the lock.
While trying to lock a TUXEDO System/T file system for exclusive access, it was discovered that another process has locked the file system, and the name of the associated lock file, filename, is printed.
No action required.
System/T provides a "null" (non-resource manager) version of the XA Transaction Interface for linking when a resource manager is not associated with a client or server. This client or server may only be involved in a group that is configured with the TMS name set to TMS and no OPENINFO string.
Change the configuration (TUXCONFIG) such that the group is properly configured, or associate the client or server with another group, or rebuild the client or server with the proper XA interface linked in using the -r option of buildserver or buildclient .
buildclient(1), buildserver(1), ubbconfig(5)
While trying to lock a TUXEDO System/T file system for exclusive access, it was discovered that another process is holding the lock.
A subsequent message will indicate the lock file. After that process holding the lock has completed, re-execute the command that failed waiting for the lock.
While trying to lock a TUXEDO System/T file system for exclusive access, it was discovered that another process has locked the file system, and the name of the associated lock file, filename, is printed.
No action required. It may be necessary to remove the lock file if the process holding the lock has died (or if the machine went down while the lock was held).
When executing rex to compile a regular expression from the pattern file, the regular expression name was longer than 30 characters in length and truncated. The first 30 characters of the name, pattern_name, are printed.
Correct the pattern file and re-execute the command.
rex(1)
When executing rex to compile a regular expression from the pattern file, the regular expression pattern was not found on an input line. Input lines must consist of optional white space followed by a name and double-quoted pattern, separated by white space.
Correct the pattern file and re-execute the command.
rex(1)
When executing rex to compile a regular expression from the pattern file, an unexpected end-of-file was found while reading a regular expression value.
Correct the pattern file and re-execute the command.
rex(1)
A null command string was given to the
bq ()
function for running in the background.
This command is no longer supported.
While dequeuing a message using
tpdequeue ,
the
_tmreinitbuf
function for the typed buffer returned an error. Check the userlog for any messages printed by
_tmreinitbuf .
Contact your BEA TUXEDO System Technical Support. One of the internal routines to manage TUXEDO System/T data structures received an
invalid parameter.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while trying to allocate space for an encryption key. Make sure the operating system parameters are set correctly
for the amount of memory on the machine and the amount of
memory that can be used by a process.
Reduce the memory usage on the machine or
increase the amount of physical memory on the machine. One of the internal routines to manage TUXEDO System/T data structures received an
invalid parameter.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. One of the internal routines to manage TUXEDO System/T data structures received an
invalid parameter.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while trying to allocate space for an encryption session key. Make sure the operating system parameters are set correctly
for the amount of memory on the machine and the amount of
memory that can be used by a process.
Reduce the memory usage on the machine or
increase the amount of physical memory on the machine. One of the internal routines to encrypt a password and generate
a session key received an invalid parameter.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while trying to allocate space for a session key. 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. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while trying to allocate space while encrypting a password
to generate a session key. 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. An attempt dynamically to allocate memory from the operating system
using
malloc ()
failed while dequeuing a message. 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. tpdequeue(3c) tpdequeue
could not get the
DIAGNOSTIC
field value from the reply message for the operation. The
tpdequeue
operation will fail.
Contact your BEA TUXEDO System Technical Support. tpdequeue(3c) tpdequeue
could not get the specified field, fieldname,
from the reply message for the operation.
The fieldname
can be "FLAGS", "CORRID", "FAILUREQ", "MSGID", "PRIORITY",
or "REPLYQ". The operation will succeed but the associated information will not be
passed back to the application from the
tpdequeue
call.
Contact your BEA TUXEDO System Technical Support. tpdequeue(3c) tpdequeue
could not set the specified field, fieldname,
in the message while performing the operation.
The fieldname
can be "FLAGS", "QNAME", or "MSGID". The operation will fail.
Contact your BEA TUXEDO System Technical Support. tpdequeue(3c) When executing
tpdequeue ,
an invalid buffer type was received internally.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. When executing
tpenqueue ,
an invalid buffer type was received internally.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. An attempt dynamically to allocate memory from the operating system
using
malloc ()
failed while enqueuing a message. 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. tpenqueue(3c) tpenqueue
could not get the
DIAGNOSTIC
field value from the reply message for the operation. The
tpenqueue
operation will fail.
Contact your BEA TUXEDO System Technical Support. tpenqueue(3c) tpenqueue
could not get the specified field, fieldname,
from the reply message for the operation.
The fieldname
can be "FLAGS" or "MSGID". The operation will succeed but the associated information will not be
passed back to the application from the
tpenqueue
call.
Contact your BEA TUXEDO System Technical Support. tpenqueue(3c) tpenqueue
could not set the specified field, fieldname,
in the message while performing the operation.
The fieldname
can be
"FLAGS" ,
"QNAME" ,
"CORRID" ,
"FAILUREQ" ,
"MSGID" ,
"PRIORITY" ,
"REPLYQ" ,
or
"TIME" . The operation will fail.
Contact your BEA TUXEDO System Technical Support. tpenqueue(3c) An attempt dynamically to reallocate an FML typed buffer using
tpalloc ()
to a smaller size
failed because the specified size was smaller than the buffer size
needed to hold the data. Reallocate the type buffer to a size that is large enough to hold
the FML data (which is returned by
Fneeded )
or re-initialize the buffer first using
Finit . Finit(3fml), Fneeded(3fml), tpalloc(3c) A routing_name
was specified for a
*SERVICE
entry in the
UBBCONFIG
file that does not appear in the
*ROUTING
section, and the standard FML routing function is used
(which requires a matching
*ROUTING
entry). Correct and re-load the
UBBCONFIG
file or provide an application-specific routing function for FML
typed buffers. typesw(5) During data-dependent routing for an FML buffer,
the specified routing_field
value in the FML buffer did not exist. Make sure the routing field is correctly set in the FML buffer. During data-dependent routing of an FML typed buffer,
the field type for the routing field didn't match the
field type for the typed buffer.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. During data-dependent routing of an FML typed buffer,
an unknown field type was encountered for the routing field.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. While doing data-dependent routing on an FML typed buffer
for the specified service,
the routing field value did not match any of the ranges specified
in the routing criteria and the criteria did not contain a wild-card
pattern. Make sure the routing field value is valid.
Correct the routing criteria in the
RANGES
value of the
UBBCONFIG
file. ubbconfig(5) While receiving a message from the network, the message size
is too small to be valid.
This should not occur during normal system operation. Check that the network is functioning properly.
Contact your BEA TUXEDO System Technical Support. While receiving a message from the network, the message contained
a release value of 0.
This should not occur during normal system operation. Check that the network is functioning properly.
Contact your BEA TUXEDO System Technical Support. While receiving a message from the network, a failure occurred in
trying to decode the header of the message.
This should not occur during normal system operation. Check that the network is functioning properly.
Contact your BEA TUXEDO System Technical Support. This message is generated by the
BRIDGE
process when the
BRIDGE
parameter is not specified in the *NETWORK section entry in the TUXEDO System/T
configuration file for a machine that is using the
TLI
transport provider (it is not necessary when using Sockets).
This message is generated by a workstation client that is using the
TLI
transport provider when the
WSDEVICE
environment variable is not
set or is set to the null string. When generated by the
BRIDGE
process, correct the TUXEDO System/T configuration file to specify a
BRIDGE
parameter.
For a /WS client,
check that the
WSDEVICE
environment variable is set correctly. ubbconfig (5) While accepting a network connection, an error occurred indicating a
bad TLI sequence number. In this case, the connection is
not explicitly disconnected. Check that the network is functioning properly. An attempt to allocate a
VIEW
typed buffer using
tpalloc
failed because the description for the view
could not be found. Add view_name
to the
VIEWFILES
(environment variable) list,
and make sure that
VIEWDIR
environment variable is set to the directory where viewfiles
can be found. tpalloc(3c), viewfile(5) An attempt to allocate a
VIEW
typed buffer using
tpalloc
failed because
the buffer length specified was smaller than the size of the view. Allocate a larger buffer based on the size of the structure associated
with the view. tpalloc(3c), viewfile(5) An attempt to re-allocate a
VIEW
typed buffer using
tprealloc
failed because the description for the view
could not be found. Add view_name
to the
VIEWFILES
(environment variable) list,
and make sure that
VIEWDIR
environment variable is set to the directory where viewfiles
can be found. tprealloc(3c), viewfile(5)P An attempt to re-allocate a
VIEW
typed buffer using
tprealloc
failed because
the buffer length specified was smaller than the size of the view. Allocate a larger buffer based on the size of the structure associated
with the view. tprealloc(3c), viewfile(5) An attempt to transmit a
VIEW
typed buffer
failed because the description for the view
could not be found. Add view_name
to the
VIEWFILES
(environment variable) list,
and make sure that
VIEWDIR
environment variable is set to the directory where viewfiles
can be found. viewfile(5) A routing_name
was specified for a
*SERVICE
entry in the
UBBCONFIG
file that does not appear in the
*ROUTING
section, and the standard VIEW routing function is used
(which requires a matching
*ROUTING
entry). Correct and re-load the
UBBCONFIG
file or provide an application-specific routing function for VIEW
typed buffers. typesw(5) Data-dependent routing failed for a
VIEW
typed buffer because the offset for the routing field is invalid.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. During data-dependent routing for a
VIEW
buffer,
the specified routing_field
value in the
VIEW
buffer was null. Make sure the routing field is correctly set in the
VIEW
buffer. During data-dependent routing of a
VIEW
typed buffer,
an unknown field type was encountered for the routing field.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. While doing data-dependent routing on a
VIEW
typed buffer
for the specified service,
the routing field value did not match any of the ranges specified
in the routing criteria and the criteria did not contain a wild-card
pattern. Make sure the routing field value is valid.
Correct the routing criteria in the
RANGES
value of the
UBBCONFIG
file. ubbconfig(5) While sending a request, the internal opcode, opcode,
was not recognized.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. While receiving a reply, the internal opcode, opcode,
was not recognized.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. One of the internal routines to manage TUXEDO System/T data structures received an
invalid parameter.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while trying to allocate space for an encryption key. Make sure the operating system parameters are set correctly
for the amount of memory on the machine and the amount of
memory that can be used by a process.
Reduce the memory usage on the machine or
increase the amount of physical memory on the machine. One of the internal routines to manage TUXEDO System/T data structures received an
invalid parameter.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. One of the internal routines to manage TUXEDO System/T data structures received an
invalid parameter.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while trying to allocate space for an encryption session key. Make sure the operating system parameters are set correctly
for the amount of memory on the machine and the amount of
memory that can be used by a process.
Reduce the memory usage on the machine or
increase the amount of physical memory on the machine. One of the internal routines to encrypt a password and generate
a session key received an invalid parameter.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while trying to allocate space for a session key. 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. An attempt to allocate a
VIEW32
typed buffer using
tpalloc
failed because the description for the view
could not be found. Add view_name
to the
VIEWFILES32
(environment variable) list,
and make sure that
VIEWDIR32
environment variable is set to the directory where viewfiles
can be found. tpalloc(3c), viewfile(5) An attempt to allocate a
VIEW32
typed buffer using
tpalloc
failed because
the buffer length specified was smaller than the size of the view. Allocate a larger buffer based on the size of the structure associated
with the view. tpalloc(3c), viewfile(5) An attempt to re-allocate a
VIEW32
typed buffer using
tprealloc
failed because the description for the view
could not be found. Add view_name
to the
VIEWFILES32
(environment variable) list,
and make sure that
VIEWDIR32
environment variable is set to the directory where viewfiles
can be found. tprealloc(3c), viewfile(5) An attempt to re-allocate a
VIEW32
typed buffer using
tprealloc
failed because
the buffer length specified was smaller than the size of the view. Allocate a larger buffer based on the size of the structure associated
with the view. tprealloc(3c), viewfile(5) An attempt to transmit a
VIEW32
typed buffer
failed because the description for the view
could not be found. Add view_name
to the
VIEWFILES32
(environment variable) list,
and make sure that
VIEWDIR32
environment variable is set to the directory where viewfiles
can be found. viewfile(5) An attempt dynamically to reallocate an FML32 typed buffer using
tpalloc ()
to a smaller size
failed because the specified size was smaller than the buffer size
needed to hold the data. Reallocate the type buffer to a size that is large enough to hold
the FML32 data (which is returned by
Fneeded32 )
or re-initialize the buffer first using
Finit32 . Finit32(3fml), Fneeded32(3fml), tpalloc32(3c) A routing_name
was specified for a
*SERVICE
entry in the
UBBCONFIG
file that does not appear in the
*ROUTING
section, and the standard FML32 routing function is used
(which requires a matching
*ROUTING
entry). Correct and re-load the
UBBCONFIG
file or provide an application-specific routing function for FML32
typed buffers. typesw(5) During data-dependent routing for an FML32 buffer,
the specified routing_field
value in the FML32 buffer did not exist. Make sure the routing field is correctly set in the FML32 buffer. During data-dependent routing of an FML32 typed buffer,
the field type for the routing field didn't match the
field type for the typed buffer.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. During data-dependent routing of an FML32 typed buffer,
an unknown field type was encountered for the routing field.
This should not occur during normal system operation. Contact your BEA TUXEDO System Technical Support. While doing data-dependent routing on an FML32 typed buffer
for the specified service,
the routing field value did not match any of the ranges specified
in the routing criteria and the criteria did not contain a wild-card
pattern. Make sure the routing field value is valid.
Correct the routing criteria in the
RANGES
value of the
UBBCONFIG
file. ubbconfig(5) The FML buffer type's
"post receive"
function failed to build
an index for a buffer just received by the process.
Although the buffer is usable, performance may be
degraded when accessing its fields. Either reduce the amount of data stored in the buffer,
or use the
FML32
buffer type instead. Findex (3c) The
FML32
buffer type's
"post receive"
function failed to build
an index for a buffer just received by the process.
Although the buffer is usable, performance may be
degraded when accessing its fields. Contact your BEA TUXEDO System Technical Support. Findex (3c) While receiving a message from the network, the message contained
an invalid release value.
This should not occur during normal system operation. Check that the network is functioning properly.
Check that the configuration does not contain much older releases of
the TUXEDO System software, connected to newer version of the software.
Contact your BEA TUXEDO System Technical Support. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while trying to prepare an FML for transport in _fpresend. 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. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while trying to prepare an FML for transport in _froute. 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. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while trying to prepare an FML32 for transport in _fpresend32. 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. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while trying to prepare an FML32 for transport in _froute32. 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. While converting a routing field to its identifier, the field could not
be found. Check the environment file for the site in question to ensure that the
environment variables FIELDTBLS and FLDTBLDIR are set
correctly for the application.
Also check that the field name is specified correctly in the ubbconfig(5) file. "BEA TUXEDO Administrator's Guide"
tmloadcf (1),
compilation (5),
ubbconfig (5) While converting a routing field to its identifier, the field could not
be found. Check the environment file for the site in question to ensure that the
environment variables FIELDTBLS and FLDTBLDIR are set
correctly for the application.
Also check that the field name is specified correctly in the ubbconfig(5) file. "BEA TUXEDO Administrator's Guide"
tmloadcf (1),
compilation (5),
ubbconfig (5) The specified filename could not be processed when
trying to set environment variables.
This may be processed when reading ENVFILE files (e.g., the
machine or server ENVFILE), when clients and servers initialize
on certain platforms, etc. Verify the specified file name to ensure that the file
exists and that the user has read permission on the file. ubbconfig(5) An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while trying to process an environment file. Make sure the operating system parameters are set correctly
for the amount of memory on the machine and the amount of
memory that can be used by a process.
Reduce the memory usage on the machine or
increase the amount of physical memory on the machine. While trying to process an environment variable file, the
specified label could not be found.
The label is specified using the -E option on most TUXEDO System
commands. Check that the label value is correct in the
environment variable file. "BEA TUXEDO Administrator's Guide" A tmadmin command was executed that has paginated output and the
paginate option is "on", but the program was unable to set up the
paginated output to the standard output.
The return code, rc, and the associated error number, errno,
are printed as part of the message. The output will not be paginated. tmadmin(1), dup(2) in UNIX reference manuals A tmadmin command was executed that has paginated output and the
paginate option is "on", but the pager command, pager, returned
an error, rc, and the associated error number, errno. This error is sometimes produced when an interrupt is received by tmadmin while paging output from a command.
Command output is terminated and execution continues with a prompt for
the next command. tmadmin(1) A tmadmin command was executed that has paginated output and the
paginate option is "on".
The starting of a separate process to run the pager (via fork())
failed with the associated error number, errno. Reset the operating system tunable parameters that limit the number of
processes in the system and/or the limit for a single user, or stop
other processes running on the system by the same user, and re-run the
command. tmadmin(1), fork(2) in UNIX reference manuals A tmadmin command was executed that has paginated output and the
paginate option is "on", but the program was unable to set up the
paginated output to the standard output.
The associated error number, errno, for the dup() system
call is printed as part of the message. The output will not be paginated. dup(2) in UNIX reference manuals A tmadmin command was executed that has paginated output and the
paginate option is "on".
The pager command, pager, completed with an abnormal return code, rc, and the associated error number, errno. This error is sometimes produced when an interrupt is received by tmadmin while paging output from a command.
Command output is terminated and execution continues with a prompt for
the next command. tmadmin(1), wait(2) in UNIX reference manuals A tmadmin command was executed that has paginated output and the
paginate option is "on", but the program was unable to set up the
paginated output to the standard output.
The associated error number, errno, is printed as part of the
message. The output will not be paginated. tmadmin(1), dup(2) in UNIX reference manuals A tmadmin command was executed that has paginated output and the
paginate option is "on", but the program was unable to set up the
paginated output to the standard output.
The return code from dup(), rc, and the associated error
number, errno, are printed as part of the message. The output will probably not be seen and it may be necessary to quit tmadmin and restart the program in order to correctly view command
output. tmadmin(1), dup(2) in UNIX reference manuals A tmadmin command was executed that has paginated output and the
paginate option is "on", but the program was unable to
create a pipe to the pager.
The associated pipe() error number, errno, is printed as
part of the message. The output will not be paginated.
The failure may be due to a limit of file descriptors for programs. tmadmin(1), pipe(2) in UNIX reference manuals An attempt dynamically to allocate memory from the operating system
using malloc() failed while starting the pager process.
The pager will not start. Make sure that the operating system parameters are set correctly for the
amount of memory that can be used by a process.
Reduce the amount of memory usage on the machine or increase the amount
of physical memory in the system. Memory allocation failed for retrieving service table entries. Make sure 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. tpsubscribe(3c) tpsubscribe(3c) couldn't insert fieldname into FML32 buffer
using Fchg32(). Contact your BEA TUXEDO System Technical Support and provide the error. tpsubscribe(3c) Memory allocation failed for retrieving service table entries. Make sure 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. tppost(3c) tppost(3c) couldn't insert fieldname into FML32 buffer
using Fchg32(). Contact your BEA TUXEDO System Technical Support. tppost(3c), Fchg(3fml) tppost(3c) couldn't insert fieldname into FML32 buffer
using Fchg32(). Contact your BEA TUXEDO System Technical Support. tppost(3c), Fchg32(3fml) Memory allocation failed for retrieving service table entries. Make sure 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. tpalloc(3c) This message indicates that posting of event eventname failed. Check the error message and take appropriate action. tppost(3c) Memory allocation failed for retrieving service table entries. Make sure 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. tpunsubscribe(3c) tpunsubscribe(3c) couldn't insert fieldname into FML32 buffer
using Fchg(). Contact your BEA TUXEDO System Technical Support and provide the error. tpunsubscribe(3c) An event was received from the network (using TLI as a provider).
The event is not a recognized value. Contact your BEA TUXEDO System Technical Support. After completing a pagination operation (from one of the
command line interpretors), an error occurred in
restoring the standard output. This may occur if the user interrups the pager processing or
another error occurs with the pager.
No action required. While trying to read the $TUXDIR/udataobj/RM file to include
a resource manager into a client or server,
the TUXDIR environment variable was not set. Set and export the TUXDIR environment variable and re-run
the operation. "BEA TUXEDO Administrator's Guide" The program was unable to read the RM file in $TUXDIR/udataobj/RM. Ensure that the TUXDIR environment variable is set correctly
and that the user has read permission on the RM file. "BEA TUXEDO Administrator's Guide" While searching $TUXDIR/udataobj/RM, an entry
for the specified RM, rmname, could not be found. Make sure that the correct RM name is specified and an
entry exists for it in $TUXDIR/udataobj/RM.
Contact your BEA TUXEDO System Technical Support. "BEA TUXEDO Administrator's Guide" An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while setting up for pagination from one of the
command interpreters on the Netware platform,
the standard output could not be re-set.
The message prints additional information regarding why the
operation failed. 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. While setting up for pagination from one of the
command interpretors on the Netware platform,
a temporary file could not be created.
The message prints additional information regarding why the
operation failed. Check the additional information printed.
The problem may be related to security, permissions, file system
space, etc.
Contact your BEA TUXEDO System Technical Support. While setting up for pagination from one of the
command interpretors on the Netware platform,
a temporary file could not be opened for writing.
The message prints additional information regarding why the
operation failed. Check the additional information printed.
The problem may be related to security, permissions, file system
space, etc.
Contact your BEA TUXEDO System Technical Support. While setting up for pagination from one of the
command interpretors on the Netware platform,
an I/O error occured.
The message prints additional information regarding why the
operation failed. Check the additional information printed.
The problem may be related to security, permissions, file system
space, etc.
Contact your BEA TUXEDO System Technical Support. While setting up for pagination from one of the
command interpretors on the Netware platform,
a temporary file could not be opened for writing.
The message prints additional information regarding why the
operation failed. Check the additional information printed.
The problem may be related to security, permissions, file system
space, etc.
Contact your BEA TUXEDO System Technical Support. While setting up for pagination from one of the
command interpretors on the Netware platform,
a temporary file could not be accessed.
The message prints additional information regarding why the
operation failed. Check the additional information printed.
The problem may be related to security, permissions, file system
space, etc.
Contact your BEA TUXEDO System Technical Support. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while setting up for pagination from one of the
command interpretors on the Netware platform. 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. While setting up for pagination from one of the
command interpretors on the Netware platform,
a temporary file could not be read correctly. Contact your BEA TUXEDO System Technical Support. An attempt dynamically to allocate memory from the operating system using
realloc ()
failed while setting up for pagination from one of the
command interpretors on the Netware platform. 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. While finishing up pagination from one of the
command interpretors on the Netware platform,
AllocateResourceTag failed for the NLM. Contact your BEA TUXEDO System Technical Support. While finishing up pagination from one of the
command interpretors on the Netware platform,
the current screen information could not be retrieved.
The message prints additional information regarding why the
operation failed. Check the additional information printed.
Contact your BEA TUXEDO System Technical Support. While finishing up pagination from one of the
command interpretors on the Netware platform,
NWSInitializeNut failed for the NLM. Contact your BEA TUXEDO System Technical Support. While finishing up pagination from one of the
command interpreters on the Netware platform,
the standard output could not be re-set.
The message prints additional information regarding why the
operation failed. Check the additional information printed.
Contact your BEA TUXEDO System Technical Support. While establishing a network connection using the socket servide
provider,
the open failed on the socket. Check that the network is configured correctly and that
sufficient resources are allocated. An internal error occurred. Contact BEA TUXEDO System Technical Support. While initializing data structures for compression, an
error occurred.
One likely cause of the error is a dynamic memory allocation failure.
Additional information is printing indicating the exact cause
of the problem. Correct the reason for the failure. While destroying data structures for compression, an
error occurred.
Additional information is printing indicating the reason for the failure. Correct the reason for the failure. While initializing data structures for compression, an
error occurred.
One likely cause of the error is a dynamic memory allocation failure.
Additional information is printing indicating the exact cause
of the problem. Correct the reason for the failure. While destroying data structures for compression, an
error occurred.
Additional information is printing indicating the reason for the failure. Correct the reason for the failure. While decompressing a message, an error occurred.
Additional information is printing indicating the reason for the failure. Correct the reason for the failure. An internal error occurred. Contact BEA TUXEDO System Technical Support. An attempt dynamically to allocate memory from the operating system
failed while trying processing a network message. 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. An attempt dynamically to allocate memory from the operating system
failed while trying processing a network message. 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. An attempt dynamically to allocate memory from the operating system
failed while trying processing a network message. 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. An attempt dynamically to allocate memory from the operating system
failed while trying processing a network message. 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. An attempt dynamically to allocate memory from the operating system
failed while trying processing a network message. 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. While processing network messages,
an internal error occurred. Contact your BEA TUXEDO System Technical Support. While processing a network message,
an invalid message header was received (with an invalid size). Check that the network is working correctly.
Contact BEA TUXEDO System Technical Support. An attempt dynamically to allocate memory from the operating system
failed while trying processing a network message. 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. An invalid event expression was detected in a subscription record. The Event Server failed to compile the event expression expr.
The error string returned from _gp_recomp() is printed in the userlog
message. tpsubscribe (3c),
_gp_recomp (3c) An attempt dynamically to allocate memory from the operating system
failed while
creating file internal storage required to compress or decompress a message.
This message is only warning when it is related to a compression request
since the message may simply be sent uncompressed.
If this situation occurs during decompression, then an
error message will
follow this one in the userlog file indicating that decompression has
failed. 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. Additionally, if a large number of files are specified to be loaded into
the file cache, then this may contribute to any memory problems experienced
in the use of
load_files .
Reduction of the file list may help alleviate
the problem. As a last resort, you may need to turn off data compression.
The use of data compression trades increased use of
CPU
and memory for decreased use of the network and/or message queues.
If memory limitations are being
reached, then compression may need to be disabled. An attempt dynamically to allocate memory from the operating system
failed while
creating file internal storage required to compress or decompress a message.
This message is only warning when it is related to a compression request
since the message may simply be sent uncompressed.
If this situation occurs during decompression, then an
error message will
follow this one in the userlog file indicating that decompression has
failed. 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. Additionally, if a large number of files are specified to be loaded into
the file cache, then this may contribute to any memory problems experienced
in the use of
load_files .
Reduction of the file list may help alleviate the problem. As a last resort, you may need to turn off data compression.
The use of data compression trades increased use of
CPU
and memory for decreased use of the network and/or message queues.
If memory limitations are being
reached, then compression may need to be disabled. "BEA TUXEDO Administrator's Guide" An attempt dynamically to allocate memory from the operating system
failed while trying to read an environment file.
Look for subsequent messages indicating the problem file. Make sure the operating system parameters are set correctly
for the amount of memory on the machine and the amount of
memory that can be used by a process.
Reduce the memory usage on the machine or
increase the amount of physical memory on the machine. While attempting to read the application password, the WSL or WSH had
a problem opening the *RESOURCES section of the TUXCONFIG file. Ensure that the TUXCONFIG environment variable points to the appropriate
configuration file. If the configuration file does not exist, it can
be created from the UBBCONFIG file using tmloadcf. If it does exist, the
file may be corrupted, or may have been a file generated by an older release
of TUXEDO System.
Shut down the system, remove the file, and recreate it with
tmloadcf. While attempting to read the application password, the WSL or WSH had
a problem reading the *RESOURCES section of the TUXCONFIG file. Ensure that the TUXCONFIG environment variable points to the appropriate
configuration file. If the configuration file does not exist, it can
be created from the UBBCONFIG file using tmloadcf. If it does exist, the
file may be corrupted, or may have been a file generated by an older release
of TUXEDO System. Shut down the system, remove the file, and recreate it with
tmloadcf. An invalid password was detected while the WSH or WSL was reading the
TUXCONFIG file. Ensure that the TUXCONFIG environment variable points to the appropriate
configuration file. If the configuration file does not exist, it can
be created from the UBBCONFIG file using tmloadcf. If it does exist, the
file may be corrupted, or may have been a file generated by an older release
of TUXEDO System. Shut down the system, remove the file, and recreate it with
tmloadcf. An invalid password was detected while the WSH or WSL was reading the
TUXCONFIG file. Ensure that the TUXCONFIG environment variable points to the appropriate
configuration file. If the configuration file does not exist, it can
be created from the UBBCONFIG file using tmloadcf. If it does exist, the
file may be corrupted, or may have been a file generated by an older release
of TUXEDO System. Shut down the system, remove the file, and recreate it with
tmloadcf. An invalid password was detected while the WSH or WSL was reading the
TUXCONFIG file. Ensure that the TUXCONFIG environment variable points to the appropriate
configuration file. If the configuration file does not exist, it can
be created from the UBBCONFIG file using tmloadcf. If it does exist, the
file may be corrupted, or may have been a file generated by an older release
of TUXEDO System. Shut down the system, remove the file, and recreate it with
tmloadcf. An error occured while encrypting the application password Contact your BEA TUXEDO System Technical Support. While creating an encryption schedule the system ran out of memory. Check the memory on the system where the process was running. An error occured while encrypting the application password Contact your BEA TUXEDO System Technical Support. An error occured while manipulating the application password Contact your BEA TUXEDO System Technical Support. While creating a key the system ran out of memory. 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. An error occured while getting a session key. Contact your BEA TUXEDO System Technical Support. While creating a session key the system ran out of memory. 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. ud or ud32 ran out of space for concurrent requests to the sytem. At most fifty request can be made simultaneously to the system from ud or
ud32. Limit the number of requests made by ud or ud32 to 50. malloc failed in the encryption subsystem 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. Could not create the object used for generating random numbers Check the memory of the system. The encryption subsystem could not find the MD5 algorithm Contact the BEA TUXEDO System Technical Support. A failure occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support. A failure occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support. A failure occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support. A memory failure occured in the encryption subsystem Make sure the operating system parameters are set correctly
for the amount of memory on the machine and the amount of
memory that can be used by a process.
Reduce the memory usage on the machine or
increase the amount of physical memory on the machine. A routine in the encryption subsystem was called in an improper context Contact the BEA TUXEDO System Technical Support. A routine in the encryption subsystem was called in an improper context Contact the BEA TUXEDO System Technical Support. An error occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support with the code number ready. A routine in the encryption subsystem was called in an improper context Contact the BEA TUXEDO System Technical Support. A routine in the encryption subsystem was called in an improper context Contact the BEA TUXEDO System Technical Support. An invalid buffer was given to the encryption subsystem Check the network. If it appears that the network is
functioning properly, then contact the BEA TUXEDO System Technical Support. An memory error occured in the encryption subsystem 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. An error occured during encryption negotiation Contact the BEA TUXEDO System Technical Support. An error occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support with the code number ready. An invalid buffer was given to the encryption subsystem Check the network. If it appears that the network is
functioning properly, then contact the BEA TUXEDO System Technical Support. An invalid buffer was given to the encryption subsystem Check the network. If it appears that the network is
functioning properly, then contact the BEA TUXEDO System Technical Support.
Make sure you have the three codes provided in the message. During the encryption negotiation process, the remote site had a fatal error. Check the diagnostic messages on the remote site. An error occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support with the code number ready. An error occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support. An error occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support with the code number ready. An error occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support. While attempting to perform an operation which requires authentication,
it was determined that the MD5 algorithm used is not available. tlisten and the processes which may attempt to contact tlisten must be
able to compute the MD5 hash of the password file. If MD5 is not available,
the authentication process cannot be completed. You must disable tlisten
authentication by removing the files $TUXDIR/udataobj/tlisten.pw and
$APPDIR/.adm/tlisten.pw. While attempting to perform an operation which requires authentication,
their was an error using the MD5 algorithm. Contact your BEA TUXEDO System Technical Support, with the values of code
and break-point. An error occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support. An error occured when getting the first Diffie-Hellman packet. Contact your BEA TUXEDO System Technical Support, with the value of handle. An error occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support. A routine in the encryption subsystem was called in an improper context Contact the BEA TUXEDO System Technical Support. A routine in the encryption subsystem was called in an improper context Contact the BEA TUXEDO System Technical Support. A routine in the encryption subsystem was called in an improper context Contact the BEA TUXEDO System Technical Support. A routine in the encryption subsystem was called in an improper context Contact the BEA TUXEDO System Technical Support. An error occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support. An error occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support. An error occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support. An error occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support. A routine in the encryption subsystem was called in an improper context Contact the BEA TUXEDO System Technical Support. A routine in the encryption subsystem was called in an improper context Contact the BEA TUXEDO System Technical Support. A routine in the encryption subsystem was called in an improper context Contact the BEA TUXEDO System Technical Support. A routine in the encryption subsystem was called in an improper context Contact the BEA TUXEDO System Technical Support. An error occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support. An error occured in the encryption subsystem Contact the BEA TUXEDO System Technical Support. An error occured in the encryption subsystem Monitor your network for malicious use. Contact your Tuxedo System
Technical Support. An error occured in the encryption subsystem Monitor your network for malicious use. Contact your Tuxedo System
Technical Support. An error occured in the encryption subsystem Monitor your network for malicious use. Contact your Tuxedo System
Technical Support. The network stream may have become corrupted Check the network. If it appears that the network is
functioning properly, then contact the BEA TUXEDO System Technical Support. The network stream may have become corrupted Check the network. If it appears that the network is
functioning properly, then contact the BEA TUXEDO System Technical Support. The FML or FML32 default routing function _froute was called, found the group
to route the request to, but found that the service service is not
offered in that group. Make sure that the routing criteria specified for the FML or FML32 buffer type
is correct. Offer service in group group. Make sure that service is not suspended. The VIEW or VIEW32 default routing function _vroute was called, found the
group to route the request to, but found that the service service is not
offered in that group. Make sure that the routing criteria specified for the VIEW or VIEW32 buffer
type is correct. Offer service in group group. Make sure that service is not suspended. While attempting to resolve the host name portion of address,
an error occured. Any address which starts with // must be a valid internet address. The
following formats are recognized by the system: //host.name:port_number
and //#.#.#.#:port_number. Other formats may be recognized. Make sure that
DNS is working properly in your network, and that the host name portion of address can be located by your DNS server. While attempting to resolve the port number portion of address,
an error occured. Any address which starts with // must be a valid internet address. The
following formats are recognized by the system: //host.name:port_number
and //#.#.#.#:port_number. Other formats may be recognized. Make sure that
DNS is working properly in your network, and that the port number portion of address can be located by your server. While attempting to resolve address, an error occured. Any address which starts with // must be a valid internet address. The
following formats are recognized by the system: //host.name:port_number
and //#.#.#.#:port_number. Other formats may be recognized. Make sure that
DNS is working properly in your network, and that the host name and
port number portion of address can be located by your server. An irregularity was detected in the encryption protocol Monitor your network for malicious use. Contact your Tuxedo System
Technical Support. An irregularity was detected in the encryption protocol Monitor your network for malicious use. Contact your Tuxedo System
Technical Support. An irregularity was detected in the encryption protocol Monitor your network for malicious use. Contact your Tuxedo System
Technical Support. An irregularity was detected in the encryption protocol Monitor your network for malicious use. Contact your Tuxedo System
Technical Support. The given address does not correspond to a type known by the system. The TUXEDO System understands several types of address format. Addresses
which start with // must be internet addresses. Addresses which start
with 0x are hexadecimal representations of the address. Other formats may
or may not be understood by the TUXEDO System. An error occured while converting address to an internal binary
representation. Contact your BEA TUXEDO System Technical Support. The port number portion of address had an illegal character. Any address which starts with // must be a valid internet address. The
following formats are recognized by the system: //host.name:port_number
and //#.#.#.#:port_number. Other formats may be recognized. port_number
may also be a symbolic name, but must only have digits or alphanumeric
letters. Change the port_number portion of address to comply with
these formats. The port number portion of address is missing. Any address which starts with // must be a valid internet address. The
following formats are recognized by the system: //host.name:port_number
and //#.#.#.#:port_number. Other formats may be recognized. port_number
may not be of zero length. Add the port_number portion of address to
comply with this formats. The port number portion of address is too large. Any address which starts with // must be a valid internet address. The
following formats are recognized by the system: //host.name:port_number
and //#.#.#.#:port_number. Other formats may be recognized. port_number
must be less than max-port. Ensure that the port_number portion of address complies with this limit. The port number portion of address had an illegal character. Any address which starts with // must be a valid internet address. The
following formats are recognized by the system: //host.name:port_number
and //#.#.#.#:port_number. Other formats may be recognized. port_number
may also be a symbolic name, but must only have digits or alphanumeric
letters. Change the port_number portion of address to comply with
these formats. The port number portion of address is missing. Any address which starts with // must be a valid internet address. The
following formats are recognized by the system: //host.name:port_number
and //#.#.#.#:port_number. Other formats may be recognized. port_number
may not be of zero length. Add the port_number portion of address to
comply with this formats. The port number portion of address is too large. Any address which starts with // must be a valid internet address. The
following formats are recognized by the system: //host.name:port_number
and //#.#.#.#:port_number. Other formats may be recognized. port_number
must be less than max-port. Ensure that the port_number portion of address complies with this limit. An internal error occurred. Contact BEA TUXEDO System Technical Support. An error occured in the encryption subsystem. Contact the BEA TUXEDO System Technical Support with the code number ready. A call to tpsubscribe(3c) failed because of permissions checking within
the EVENT_MIB(5). Check and possibly retune the permissions on the EVENT_MIB object being
accessed. For example, if you are subscribing to have a service called
when an event occurs, check the T_EVENT_SERVICE class in the EVENT_MIB. Unable to set the given field in an FML32 buffer for tpunsubscribe. The
given ferror may give insight into the reason for the failure. Contact your BEA TUXEDO System Technical Support. Unable to set the given field in an FML32 buffer for tpsubscribe. The
given ferror may give insight into the reason for the failure. Contact your BEA TUXEDO System Technical Support. Unable to set the given field in an FML32 buffer for tppost. The
given ferror may give insight into the reason for the failure. Contact your BEA TUXEDO System Technical Support. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed in the generic handler. 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. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed in the generic handler. 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. An attempt dynamically to allocate memory from the operating system using
malloc ()
failed in the generic handler. 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. Unable to set the given field in an FML32 buffer for tppost. Contact your BEA TUXEDO System Technical Support. The environment variable TMCMPPRFM may be set to a level between zero and nine.
The lower the number, the worse the compression, but the better CPU utilization.
Hence, a value of nine will give the best possible compression at the expense
of CPU utilization, whereas a value of one will give the worst compression
with the best CPU utilization. The default value is one, as the compression
achieved with this level is acceptable in most scenarios. None.DESCRIPTION
ACTION
1006 ERROR: _tmreinitbuf returned failure
DESCRIPTION
ACTION
1007 ERROR: Invalid parameter passed to internal routine
DESCRIPTION
ACTION
1008 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1009 ERROR: Invalid parameter passed to internal routine
DESCRIPTION
ACTION
1010 ERROR: Invalid parameter passed to internal routine
DESCRIPTION
ACTION
1011 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1012 ERROR: Invalid parameter passed to internal routine
DESCRIPTION
ACTION
1013 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1014 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1015 ERROR: tpdequeue - Memory allocation failure
DESCRIPTION
ACTION
SEE ALSO
1016 ERROR: [tpdequeue - failed to get DIAGNOSTIC field from tpdequeue message]
DESCRIPTION
ACTION
SEE ALSO
1017 WARN: [tpdequeue - failed to get fieldname field from tpdequeue message]
DESCRIPTION
ACTION
SEE ALSO
1018 ERROR: [tpdequeue - failed to set fieldname field for tpdequeue message]
DESCRIPTION
ACTION
SEE ALSO
1019 ERROR: [tpdequeue - invalid internal buffer type]
DESCRIPTION
ACTION
1020 ERROR: [tpenqueue - invalid internal buffer type]
DESCRIPTION
ACTION
1021 ERROR: tpenqueue - Memory allocation failure
DESCRIPTION
ACTION
SEE ALSO
1022 ERROR: [tpenqueue - failed to get DIAGNOSTIC field from tpenqueue message]
DESCRIPTION
ACTION
SEE ALSO
1023 WARN: [tpenqueue - failed to get fieldname field from tpenqueue message]
DESCRIPTION
ACTION
SEE ALSO
1024 ERROR: [tpenqueue - failed to set fieldname field for tpenqueue message]
DESCRIPTION
ACTION
SEE ALSO
1025 ERROR: Cannot reallocate FML buffer to smaller than its unindexed size
DESCRIPTION
ACTION
SEE ALSO
1026 ERROR: tmroute failed, could not find routing criteria of routing_name for buffer type FML
DESCRIPTION
ACTION
SEE ALSO
1027 ERROR: Routing field for 'routing_field' null
DESCRIPTION
ACTION
1028 ERROR: Field type of buffer does not match routing criteria type
DESCRIPTION
ACTION
1029 ERROR: Unknown field type used for FML routing
DESCRIPTION
ACTION
1030 ERROR: Routing field value for 'service' not valid
DESCRIPTION
ACTION
SEE ALSO
1031 ERROR: Bad header from network, size=size
DESCRIPTION
ACTION
1032 ERROR: Bad header from network, release=release
DESCRIPTION
ACTION
1034 ERROR: Error decoding BRIDGE RPC msg
DESCRIPTION
ACTION
1035 ERROR: Network device not specified
DESCRIPTION
ACTION
SEE ALSO
1036 ERROR: Bad TLI Call sequence number seq, Will not send disconnect sequence
DESCRIPTION
ACTION
1037 ERROR: Unable to find view file for type view_name
DESCRIPTION
ACTION
SEE ALSO
1038 ERROR: Insufficient space allocated for type view_name
DESCRIPTION
ACTION
SEE ALSO
1039 ERROR: Unable to find view file for type view_name
DESCRIPTION
ACTION
SEE ALSO
1040 ERROR: Insufficient space reallocated for type view_name
DESCRIPTION
ACTION
SEE ALSO
1041 ERROR: Can't find view file for type view_name
DESCRIPTION
ACTION
SEE ALSO
1042 ERROR: tmroute failed, could not find routing criteria of routing_name for buffer type type subtype view_name
DESCRIPTION
ACTION
SEE ALSO
1043 ERROR: Illegal offset value for view_name
DESCRIPTION
ACTION
1044 ERROR: Routing field for 'routing_field' null
DESCRIPTION
ACTION
1046 ERROR: Unknown field type used for routing
DESCRIPTION
ACTION
1047 ERROR: Routing field value for 'service' not valid
DESCRIPTION
ACTION
SEE ALSO
1048 ERROR: Don't know how to encode/decode data for request opcode 0xopcode
DESCRIPTION
ACTION
1049 ERROR: Don't know how to encode/decode data for reply opcode 0xopcode
DESCRIPTION
ACTION
1050 ERROR: Invalid parameter
DESCRIPTION
ACTION
1051 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1052 ERROR: Invalid parameter
DESCRIPTION
ACTION
1053 ERROR: Invalid parameter
DESCRIPTION
ACTION
1054 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1055 ERROR: Invalid parameter
DESCRIPTION
ACTION
1056 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1057 ERROR: Unable to find view file for VIEW32 view_name
DESCRIPTION
ACTION
SEE ALSO
1058 ERROR: Insufficient space allocated for VIEW32 view_name
DESCRIPTION
ACTION
SEE ALSO
1059 ERROR: Unable to find view file for VIEW32 view_name
DESCRIPTION
ACTION
SEE ALSO
1060 ERROR: Insufficient space reallocated for VIEW32 view_name
DESCRIPTION
ACTION
SEE ALSO
1061 ERROR: Can't find VIEW32 file for view view_name
DESCRIPTION
ACTION
SEE ALSO
1062 ERROR: Cannot reallocate FML buffer to smaller than its unindexed size
DESCRIPTION
ACTION
SEE ALSO
1063 ERROR: tmroute failed, could not find routing criteria of routing_name for buffer type FML32
DESCRIPTION
ACTION
SEE ALSO
1064 ERROR: Routing field for 'routing_field' null
DESCRIPTION
ACTION
1065 ERROR: Field type of buffer does not match routing criteria type
DESCRIPTION
ACTION
1066 ERROR: Unknown field type used for FML32 routing
DESCRIPTION
ACTION
1067 ERROR: Routing field value for 'service' not valid
DESCRIPTION
ACTION
SEE ALSO
1068 WARN: Could not index FML buffer in postrecv
DESCRIPTION
ACTION
SEE ALSO
1069 WARN: Could not index FML32 buffer in postrecv
DESCRIPTION
ACTION
SEE ALSO
1070 ERROR: Received message with unknown release number release
DESCRIPTION
ACTION
1071 ERROR: Memory allocation failure resynchronizing buffer
DESCRIPTION
ACTION
1072 ERROR: Memory allocation failure resynchronizing buffer
DESCRIPTION
ACTION
1073 ERROR: Memory allocation failure resynchronizing FML32 buffer
DESCRIPTION
ACTION
1074 ERROR: Memory allocation failure resynchronizing FML32 buffer
DESCRIPTION
ACTION
1075 ERROR: tmroute failed, invalid field identifier for routing criteria routing_name
DESCRIPTION
ACTION
SEE ALSO
1076 ERROR: tmroute failed, invalid field identifier for routing criteria routing_name
DESCRIPTION
ACTION
SEE ALSO
1077 ERROR: Unable to open environment file filename for reading
DESCRIPTION
ACTION
SEE ALSO
1078 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1079 WARN: Label label not found in environment file
DESCRIPTION
ACTION
SEE ALSO
1080 ERROR: child dup error, rc=rc, errno=errno
DESCRIPTION
ACTION
SEE ALSO
1081 ERROR: pager: return code 0xrc, errno=errno
DESCRIPTION
ACTION
SEE ALSO
1082 ERROR: could not fork, errno=errno
DESCRIPTION
ACTION
SEE ALSO
1083 ERROR: parent dup error while saving stdout, errno=errno
DESCRIPTION
ACTION
SEE ALSO
1084 ERROR: pager: wait status 0xrc, errno=errno
DESCRIPTION
ACTION
SEE ALSO
1085 ERROR: parent dup error for pipe, rc=rc, errno=errno
DESCRIPTION
ACTION
SEE ALSO
1086 ERROR: restore dup error, rc=rc, errno=errno
DESCRIPTION
ACTION
SEE ALSO
1087 ERROR: could not make pipe, errno=errno
DESCRIPTION
ACTION
SEE ALSO
1088 ERROR: malloc failed, errno=errno
DESCRIPTION
ACTION
1089 ERROR: tpsubscribe - Memory allocation failure
DESCRIPTION
ACTION
SEE ALSO
1090 ERROR: [tpsubscribe - failed to set fieldname field for tpsubscribe message. Ferror32=error]
DESCRIPTION
ACTION
SEE ALSO
1091 ERROR: tppost - Memory allocation failure
DESCRIPTION
ACTION
SEE ALSO
1092 ERROR: [tppost - failed to set fieldname field for tppost message]
DESCRIPTION
ACTION
SEE ALSO
1093 ERROR: tppost - Can't add field fieldname to FML32 buffer
DESCRIPTION
ACTION
SEE ALSO
1094 ERROR: tpalloc failed. error=error
DESCRIPTION
ACTION
SEE ALSO
1095 ERROR: tppost failed when posting event eventname, tperrmsg=<errmsg>, dropping the message
DESCRIPTION
ACTION
SEE ALSO
1096 ERROR: tpunsubscribe - Memory allocation failure
DESCRIPTION
ACTION
SEE ALSO
1097 ERROR: [tpunsubscribe - failed to set fieldname field for tpunsubscribe message. Ferror32=error]
DESCRIPTION
ACTION
SEE ALSO
1098 ERROR: Unexpected TLI return number val
DESCRIPTION
ACTION
1099 ERROR: restore dup error, rc=return, errno=errno_val
DESCRIPTION
ACTION
GP MESSAGES 1100-1199
1100 ERROR: TUXDIR environment variable not set
DESCRIPTION
ACTION
SEE ALSO
1101 ERROR: Cannot open file filename
DESCRIPTION
ACTION
SEE ALSO
1102 ERROR: Cannot find RM rmname in file filename
DESCRIPTION
ACTION
SEE ALSO
1103 ERROR: Can't allocate space for _gp_pgHand struct
DESCRIPTION
ACTION
1104 ERROR: Can't create temporary paging file, error_info
DESCRIPTION
ACTION
1105 ERROR: Can't open temporary paging file filename for writing, error_info
DESCRIPTION
ACTION
1106 ERROR: Can't reopen temporary paging file filename as stdout, error_info
DESCRIPTION
ACTION
1107 ERROR: Can't open temporary paging file filename for reading, error_info
DESCRIPTION
ACTION
1108 ERROR: Can't get status of temporary paging file filename, error_info
DESCRIPTION
ACTION
1109 ERROR: Can't allocate num bytes for paging
DESCRIPTION
ACTION
1110 ERROR: Error in processing temporary paging file filename
DESCRIPTION
ACTION
1111 ERROR: Can't reallocate num bytes for paging
DESCRIPTION
ACTION
1112 ERROR: AllocateResourceTag failed
DESCRIPTION
ACTION
1113 ERROR: Invalid current screen, error_info
DESCRIPTION
ACTION
1114 ERROR: NWSInitializeNut failed
DESCRIPTION
ACTION
1115 ERROR: Can't reopen stdout, error_info
DESCRIPTION
ACTION
1116 ERROR: Can't open socket.
DESCRIPTION
ACTION
GP MESSAGES 1200-1299
1200 ERROR: Invalid length passed to _tuxdftcmpexp
DESCRIPTION
ACTION
1201 ERROR: Failed to initialize deflate structure: (error/error_info)
DESCRIPTION
ACTION
1202 ERROR: Failed to destroy deflate structure: (error/error_info)
DESCRIPTION
ACTION
1203 ERROR: Failed to initialize inflate structure: (error/error_info)
DESCRIPTION
ACTION
1204 ERROR: Failed to destroy inflate structure: (error/error_info)
DESCRIPTION
ACTION
1205 ERROR: Failed to decompress message: (error/error_info)
DESCRIPTION
ACTION
1206 ERROR: Invalid opcode val passed to _tuxdftcmpexp
DESCRIPTION
ACTION
1207 ERROR: Memory allocation error
DESCRIPTION
ACTION
1208 ERROR: Memory allocation error
DESCRIPTION
ACTION
1209 ERROR: Memory allocation error: error_info
DESCRIPTION
ACTION
1210 ERROR: Memory allocation error: error_info
DESCRIPTION
ACTION
1211 ERROR: Memory allocation error: error_info
DESCRIPTION
ACTION
1212 ERROR: Could not expand multiple messages
DESCRIPTION
ACTION
1213 ERROR: Bad header from network, size=size
DESCRIPTION
ACTION
1214 ERROR: Memory allocation error: error_info
DESCRIPTION
ACTION
1215 ERROR: Cannot compile event expression expr, error=errstr
DESCRIPTION
ACTION
SEE ALSO
1216 WARN: Memory allocation failure
DESCRIPTION
ACTION
1217 WARN: Memory allocation failure
DESCRIPTION
ACTION
SEE ALSO
1218 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1219 ERROR: Unable to open TUXCONFIG file to Resources section
DESCRIPTION
ACTION
1220 ERROR: Unable to open Resources section of TUXCONFIG file
DESCRIPTION
ACTION
1221 ERROR: Possibly corrupted key in database
DESCRIPTION
ACTION
1222 ERROR: Error while decrypting password
DESCRIPTION
ACTION
1223 ERROR: Invalid password in TUXCONFIG file
DESCRIPTION
ACTION
1224 ERROR: Invalid parameter
DESCRIPTION
ACTION
1225 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1226 ERROR: Invalid parameter
DESCRIPTION
ACTION
1227 ERROR: Invalid parameter
DESCRIPTION
ACTION
1228 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1229 ERROR: Invalid parameter
DESCRIPTION
ACTION
1230 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1231 ERROR: Reply queue full
DESCRIPTION
ACTION
1232 ERROR: Memory allocation failure
DESCRIPTION
ACTION
1233 ERROR: Could not create random algorithm object
DESCRIPTION
ACTION
1234 ERROR: Could not use MD5 random algorithm
DESCRIPTION
ACTION
1235 ERROR: Could not initialize random algorithm
DESCRIPTION
ACTION
1236 ERROR: Could not get random seed
DESCRIPTION
ACTION
1237 ERROR: Could not update random algorithm
DESCRIPTION
ACTION
1238 ERROR: Memory allocation error
DESCRIPTION
ACTION
1239 ERROR: New encryption buffer, but offset(offset) is not zero
DESCRIPTION
ACTION
1240 ERROR: Invalid attempt to use 40-bit encryption
DESCRIPTION
ACTION
1241 ERROR: An error occured in the encryption subsystem code(code)
DESCRIPTION
ACTION
1242 ERROR: New encryption buffer, but offset(offset) is not zero
DESCRIPTION
ACTION
1243 ERROR: Invalid attempt to use 40-bit encryption
DESCRIPTION
ACTION
1244 ERROR: Invalid packet from network
DESCRIPTION
ACTION
1245 ERROR: Memory allocation error
DESCRIPTION
ACTION
1246 ERROR: Could not generate negative encryption packet
DESCRIPTION
ACTION
1247 ERROR: An error occured in the encryption subsystem code (code)
DESCRIPTION
ACTION
1248 ERROR: The encryption packet is invalid
DESCRIPTION
ACTION
1249 ERROR: Invalid packet from network (0xnum, num, num)
DESCRIPTION
ACTION
1251 ERROR: Remote system returns an error (code)
DESCRIPTION
ACTION
1252 ERROR: An error occured in the encryption subsystem code (code)
DESCRIPTION
ACTION
1253 ERROR: Invalid number of encryption bits
DESCRIPTION
ACTION
1254 ERROR: An error occured in the encryption subsystem code (code)
DESCRIPTION
ACTION
1258 ERROR: internal error
DESCRIPTION
ACTION
1259 ERROR: Cannot authenticate, encryption is unavailable
DESCRIPTION
ACTION
1260 ERROR: Encryption failure code at break point break-point
DESCRIPTION
ACTION
1261 ERROR: Badly aligned offset(offset) value
DESCRIPTION
ACTION
1262 ERROR: Bad encryption handle(handle)
DESCRIPTION
ACTION
1263 ERROR: Encryption handle in unexpected state string
DESCRIPTION
ACTION
1264 ERROR: Invalid attempt to use 128-bit encryption
DESCRIPTION
ACTION
1265 ERROR: Invalid attempt to use 128-bit encryption
DESCRIPTION
ACTION
1266 ERROR: Invalid attempt to use 40-bit encryption
DESCRIPTION
ACTION
1267 ERROR: Invalid attempt to use 128-bit encryption
DESCRIPTION
ACTION
1268 ERROR: Badly aligned offset(offset) value
DESCRIPTION
ACTION
1269 ERROR: The encryption packet is invalid
DESCRIPTION
ACTION
1270 ERROR: Bad encryption handle(num)
DESCRIPTION
ACTION
1271 ERROR: Encryption handle in unexpected state string
DESCRIPTION
ACTION
1272 ERROR: Invalid attempt to use 128-bit encryption
DESCRIPTION
ACTION
1273 ERROR: Invalid attempt to use 128-bit encryption
DESCRIPTION
ACTION
1274 ERROR: Invalid attempt to use 40-bit encryption
DESCRIPTION
ACTION
1275 ERROR: Invalid attempt to use 128-bit encryption
DESCRIPTION
ACTION
1276 ERROR: Bad encryption handle(num)
DESCRIPTION
ACTION
1277 ERROR: Encryption handle in unexpected state string
DESCRIPTION
ACTION
1278 ERROR: Invalid negotiation parameter from remote site
DESCRIPTION
ACTION
1279 ERROR: Invalid negotiation parameter from remote site
DESCRIPTION
ACTION
1280 ERROR: Invalid negotiation parameter from remote site
DESCRIPTION
ACTION
1281 ERROR: Received message with invalid release number num
DESCRIPTION
ACTION
1282 ERROR: Received message with invalid release number num
DESCRIPTION
ACTION
1283 ERROR: Service service not available in group gname
DESCRIPTION
ACTION
1284 ERROR: Service service not available in group gname
DESCRIPTION
ACTION
1285 ERROR: Can't resolve host name in address address
DESCRIPTION
ACTION
1286 ERROR: Can't resolve port number in address address
DESCRIPTION
ACTION
1287 ERROR: Can't parse the address address
DESCRIPTION
ACTION
1288 ERROR: Invalid parameter from remote site
DESCRIPTION
ACTION
1289 ERROR: Invalid parameter from remote site
DESCRIPTION
ACTION
1290 ERROR: Invalid parameter from remote site
DESCRIPTION
ACTION
1291 ERROR: Invalid parameter from remote site
DESCRIPTION
ACTION
1292 ERROR: Unknown address type: address
DESCRIPTION
ACTION
1293 ERROR: Can't convert the address address to binary format
DESCRIPTION
ACTION
1294 ERROR: Illegal character in the address address
DESCRIPTION
ACTION
1295 ERROR: Missing port number in the address address
DESCRIPTION
ACTION
1296 ERROR: Port number cant be bigger than max-port in the address address
DESCRIPTION
ACTION
1297 ERROR: Illegal character in the address address
DESCRIPTION
ACTION
1298 ERROR: Missing port number in the address address
DESCRIPTION
ACTION
1299 ERROR: Port number cant be bigger than max-port in the address address
DESCRIPTION
ACTION
GP MESSAGES 1300-1399
1303 ERROR: Invalid internal buffer: error
DESCRIPTION
ACTION
1304 ERROR: An error occured in the encryption subsystem code (code)
DESCRIPTION
ACTION
1305 ERROR: tpsubscribe failed to due a permissions violation in the EVENT_MIB
DESCRIPTION
ACTION
1307 ERROR: [tpunsubscribe - failed to set field field for tpunsubscribe message. Ferror32=ferror]
DESCRIPTION
ACTION
1308 ERROR: [tpsubscribe - failed to set field field for tpsubscribe message. Ferror32= ferror]
DESCRIPTION
ACTION
1309 ERROR: [tppost - failed to set field field for tppost message]
DESCRIPTION
ACTION
1310 ERROR: tppost - Memory allocation failure
DESCRIPTION
ACTION
1311 ERROR: tpsubscribe - Memory allocation failure
DESCRIPTION
ACTION
1312 ERROR: tpunsubscribe - Memory allocation failure
DESCRIPTION
ACTION
1313 ERROR: tppost - Can't add field field to FML32 buffer
DESCRIPTION
ACTION
1314 INFO: Compression Level set to level
DESCRIPTION
ACTION