1001
WARN: rex: name pattern_name truncated
Description
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.
rex
Action
Correct the pattern file and re-execute the command.
See Also
rex(1)
1002
ERROR: rex: missing regular expression value for name pattern_name
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.
1003
ERROR: rex: unexpected end of file
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.
1006
ERROR: _tmreinitbuf returned failure
While dequeuing a message using tpdequeue, the _tmreinitbuf function for the typed buffer returned an error.
tpdequeue
_tmreinitbuf
Check the userlog for any messages printed by _tmreinitbuf. Contact your BEA TUXEDO system Technical Support.
1007
ERROR: Invalid parameter passed to internal routine
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.
1008
ERROR: Memory allocation failure
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to allocate space for an encryption key.
malloc()
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.
1009
1010
One of the internal routines to manage BEA TUXEDO data structures received an invalid parameter. This should not occur during normal system operation.
1011
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to allocate space for an encryption session key.
1012
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.
1013
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to allocate space for a session key.
1014
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.
1015
ERROR: tpdequeue - Memory allocation failure
An attempt dynamically to allocate memory from the operating system using malloc() failed while dequeuing a message.
tpdequeue(3c)
1016
ERROR: [tpdequeue - failed to get DIAGNOSTIC field from tpdequeue message]
tpdequeue could not get the DIAGNOSTIC field value from the reply message for the operation.
DIAGNOSTIC
The tpdequeue operation will fail. Contact your BEA TUXEDO system Technical Support.
1017
WARN: [tpdequeue - failed to get fieldname field from tpdequeue message]
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.
1018
ERROR: [tpdequeue - failed to set fieldname field for tpdequeue message]
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.
1019
ERROR: [tpdequeue - invalid internal buffer type]
When executing tpdequeue, an invalid buffer type was received internally. This should not occur during normal system operation.
1020
ERROR: [tpenqueue - invalid internal buffer type]
When executing tpenqueue, an invalid buffer type was received internally. This should not occur during normal system operation.
tpenqueue
1021
ERROR: tpenqueue - Memory allocation failure
An attempt dynamically to allocate memory from the operating system using malloc() failed while enqueuing a message.
tpenqueue(3c)
1022
ERROR: [tpenqueue - failed to get DIAGNOSTIC field from tpenqueue message]
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.
1023
WARN: [tpenqueue - failed to get fieldname field from tpenqueue message]
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.
1024
ERROR: [tpenqueue - failed to set fieldname field for tpenqueue message]
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".
1025
ERROR: Cannot reallocate FML buffer to smaller than its unindexed size
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.
tpalloc()
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.
Fneeded
Finit
Finit(3fml), Fneeded(3fml), tpalloc(3c)
tpalloc
1026
ERROR: tmroute failed, could not find routing criteria of routing_name for buffer type FML
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).
SERVICE
ROUTING
Correct and re-load the UBBCONFIG file or provide an application-specific routing function for FML typed buffers.
typesw(5)
typesw
1027
ERROR: Routing field for 'routing_field' null
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.
1028
ERROR: Field type of buffer does not match routing criteria type
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.
1029
ERROR: Unknown field type used for FML routing
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.
1030
ERROR: Routing field value for 'service' not valid
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.
RANGES
UBBCONFIG
ubbconfig(5)
ubbconfig
1031
ERROR: Bad header from network, size=size
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.
1032
ERROR: Bad header from network, release=release
While receiving a message from the network, the message contained a release value of 0. This should not occur during normal system operation.
1034
ERROR: Error decoding BRIDGE RPC msg
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.
1035
ERROR: Network device not specified
This message is generated by the BRIDGE process when the BRIDGE parameter is not specified in the NETWORK section entry in the BEA TUXEDO configuration file for a machine that is using the TLI transport provider (it is not necessary when using Sockets).
BRIDGE
NETWORK
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.
TLI
WSDEVICE
When generated by the BRIDGE process, correct the BEA TUXEDO system configuration file to specify a BRIDGE parameter.
For a /WS client, check that the WSDEVICE environment variable is set correctly.
1036
ERROR: Bad TLI Call sequence number seq, Will not send disconnect sequence
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.
1037
ERROR: Unable to find view file for type view_name
An attempt to allocate a VIEW typed buffer using tpalloc failed because the description for the view could not be found.
VIEW
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.
VIEWFILES
VIEWDIR
tpalloc(3c), viewfile(5)
viewfile
1038
ERROR: Insufficient space allocated for type view_name
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.
1039
An attempt to re-allocate a VIEW typed buffer using tprealloc failed because the description for the view could not be found.
tprealloc
tprealloc(3c), viewfile(5)
1040
ERROR: Insufficient space reallocated for type view_name
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.
1041
ERROR: Can't find view file for type view_name
An attempt to transmit a VIEW typed buffer failed because the description for the view could not be found.
viewfile(5)
1042
ERROR: tmroute failed, could not find routing criteria of routing_name for buffer type type subtype view_name
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.
1043
ERROR: Illegal offset value for view_name
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.
1044
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.
1046
ERROR: Unknown field type used for routing
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.
1047
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.
1048
ERROR: Don't know how to encode/decode data for request opcode 0xopcode
While sending a request, the internal opcode, opcode, was not recognized. This should not occur during normal system operation.
1049
ERROR: Don't know how to encode/decode data for reply opcode 0xopcode
While receiving a reply, the internal opcode, opcode, was not recognized. This should not occur during normal system operation.
1050
ERROR: Invalid parameter
1051
1052
1053
1054
1055
1056
1057
ERROR: Unable to find view file for VIEW32 view_name
An attempt to allocate a VIEW32 typed buffer using tpalloc failed because the description for the view could not be found.
VIEW32
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.
VIEWFILES32
VIEWDIR32
1058
ERROR: Insufficient space allocated for VIEW32 view_name
An attempt to allocate a VIEW32 typed buffer using tpalloc failed because the buffer length specified was smaller than the size of the view.
1059
An attempt to re-allocate a VIEW32 typed buffer using tprealloc failed because the description for the view could not be found.
1060
ERROR: Insufficient space reallocated for VIEW32 view_name
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.
1061
ERROR: Can't find VIEW32 file for view view_name
An attempt to transmit a VIEW32 typed buffer failed because the description for the view could not be found.
1062
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.
Fneeded32
Finit32
Finit32(3fml), Fneeded32(3fml), tpalloc32(3c)
tpalloc32
1063
ERROR: tmroute failed, could not find routing criteria of routing_name for buffer type FML32
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.
1064
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.
1065
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.
1066
ERROR: Unknown field type used for FML32 routing
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.
1067
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.
1068
WARN: Could not index FML buffer in postrecv
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.
post receive
Either reduce the amount of data stored in the buffer, or use the FML32 buffer type instead.
Findex(3fml)
Findex
1069
WARN: Could not index FML32 buffer in postrecv
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.
1070
ERROR: Received message with unknown release number release
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 BEA TUXEDO software, connected to newer version of the software. Contact your BEA TUXEDO system Technical Support.
1071
ERROR: Memory allocation failure resynchronizing buffer
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to prepare an FML for transport in _fpresend.
1072
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to prepare an FML for transport in _froute.
1073
ERROR: Memory allocation failure resynchronizing FML32 buffer
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to prepare an FML32 for transport in _fpresend32.
1074
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to prepare an FML32 for transport in _froute32.
1075
ERROR: tmroute failed, invalid field identifier for routing criteria routing_name
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.
FIELDTBLS
FLDTBLDIR
BEA TUXEDO Administrator's Guide, tmloadcf(1), compilation(5), ubbconfig(5)
tmloadcf
compilation
1076
1077
ERROR: Unable to open environment file filename for reading
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.
1078
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to process an environment file.
1079
WARN: Label label not found in environment file
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 BEA TUXEDO system commands.
Check that the label value is correct in the environment variable file.
BEA TUXEDO Administrator's Guide
1080
ERROR: child dup error, rc=rc, errno=errno
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.
tmadmin
The output will not be paginated.
tmadmin(1), dup(2) in UNIX reference manuals
dup
1081
ERROR: pager: return code 0xrc, errno=errno
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.
pager
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)
1082
ERROR: could not fork, errno=errno
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.
fork()
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
fork
1083
ERROR: parent dup error while saving stdout, errno=errno
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.
dup()
dup(2) in UNIX reference manuals
1084
ERROR: pager: wait status 0xrc, errno=errno
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.
tmadmin(1), wait(2) in UNIX reference manuals
wait
1085
ERROR: parent dup error for pipe, rc=rc, errno=errno
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.
1086
ERROR: restore dup error, rc=rc, errno=errno
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.
1087
ERROR: could not make pipe, errno=errno
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.
pipe()
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
pipe
1088
ERROR: malloc failed, errno=errno
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.
1089
ERROR: tpsubscribe - Memory allocation failure
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
1090
ERROR: [tpsubscribe - failed to set fieldname field for tpsubscribe message. Ferror32=error]
tpsubscribe(3c) couldn't insert fieldname into FML32 buffer using Fchg32().
Fchg32()
Contact your BEA TUXEDO system Technical Support and provide the error.
1091
ERROR: tppost - Memory allocation failure
tppost(3c)
tppost
1092
ERROR: [tppost - failed to set fieldname field for tppost message]
tppost(3c) couldn't insert fieldname into FML32 buffer using Fchg32().
tppost(3c), Fchg(3fml)
Fchg
1093
ERROR: tppost - Can't add field fieldname to FML32 buffer
tppost(3c), Fchg32(3fml)
Fchg32
1094
ERROR: tpalloc failed. error=error
tpalloc(3c)
1095
ERROR: tppost failed when posting event eventname, tperrmsg=errmsg, dropping the message
This message indicates that posting of event eventname failed.
Check the error message and take appropriate action.
1096
ERROR: tpunsubscribe - Memory allocation failure
tpunsubscribe(3c)
tpunsubscribe
1097
ERROR: [tpunsubscribe - failed to set fieldname field for tpunsubscribe message. Ferror32=error]
tpunsubscribe(3c) couldn't insert fieldname into FML32 buffer using Fchg().
Fchg()
1098
ERROR: Unexpected TLI return number val
An event was received from the network (using TLI as a provider). The event is not a recognized value.
1099
ERROR: restore dup error, rc=return, errno=errno_val
After completing a pagination operation (from one of the command line interpreters), an error occurred in restoring the standard output.
This may occur if the user interrupts the pager processing or another error occurs with the pager. No action required.