GP Messages 1000-1099
|
|
|
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.
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
Description
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.
Action
Correct the pattern file and re-execute the command.
See Also
rex(1)
1003
ERROR: rex: unexpected end of file
Description
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.
Action
Correct the pattern file and re-execute the command.
See Also
rex(1)
1007
ERROR: Invalid parameter passed to internal routine
Description
One of the internal routines to manage TUXEDO System/T data structures received an invalid parameter. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
1008
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to allocate space for an encryption key.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1009
ERROR: Invalid parameter passed to internal routine
Description
One of the internal routines to manage TUXEDO System/T data structures received an invalid parameter. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
1010
ERROR: Invalid parameter passed to internal routine
Description
One of the internal routines to manage BEA TUXEDO data structures received an invalid parameter. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
1011
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to allocate space for an encryption session key.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1012
ERROR: Invalid parameter passed to internal routine
Description
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.
Action
Contact your BEA TUXEDO system Technical Support.
1013
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to allocate space for a session key.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1014
ERROR: Memory allocation failure
Description
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.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1016
ERROR: [tpdequeue - failed to get DIAGNOSTIC field from tpdequeue message]
Description
tpdequeue could not get the DIAGNOSTIC field value from the reply message for the operation.
Action
The tpdequeue operation will fail. Contact your BEA TUXEDO system Technical Support.
See Also
tpdequeue(3c)
1017
WARN: [tpdequeue - failed to get fieldname field from tpdequeue message]
Description
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".
Action
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.
See Also
tpdequeue(3c)
1018
ERROR: [tpdequeue - failed to set fieldname field for tpdequeue message]
Description
tpdequeue could not set the specified field, fieldname, in the message while performing the operation. The fieldname can be "FLAGS", "QNAME", or "MSGID".
Action
The operation will fail. Contact your BEA TUXEDO system Technical Support.
See Also
tpdequeue(3c)
1019
ERROR: [tpdequeue - invalid internal buffer type]
Description
When executing tpdequeue, an invalid buffer type was received internally. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
1020
ERROR: [tpenqueue - invalid internal buffer type]
Description
When executing tpenqueue, an invalid buffer type was received internally. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
1022
ERROR: [tpenqueue - failed to get DIAGNOSTIC field from tpenqueue message]
Description
tpenqueue could not get the DIAGNOSTIC field value from the reply message for the operation.
Action
The tpenqueue operation will fail. Contact your BEA TUXEDO system Technical Support.
See Also
tpenqueue(3c)
1023
WARN: [tpenqueue - failed to get fieldname field from tpenqueue message]
Description
tpenqueue could not get the specified field, fieldname, from the reply message for the operation. The fieldname can be "FLAGS" or "MSGID".
Action
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.
See Also
tpenqueue(3c)
1024
ERROR: [tpenqueue - failed to set fieldname field for tpenqueue message]
Description
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".
Action
The operation will fail. Contact your BEA TUXEDO system Technical Support.
See Also
tpenqueue(3c)
1025
ERROR: Cannot reallocate FML buffer to smaller than its unindexed size
Description
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.
Action
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.
See Also
Finit(3fml), Fneeded(3fml), tpalloc(3c)
1026
ERROR: tmroute failed, could not find routing criteria of routing_name for buffer type FML
Description
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).
Action
Correct and re-load the UBBCONFIG file or provide an application-specific routing function for FML typed buffers.
See Also
typesw(5)
1027
ERROR: Routing field for 'routing_field' null
Description
During data-dependent routing for an FML buffer, the specified routing_field value in the FML buffer did not exist.
Action
Make sure the routing field is correctly set in the FML buffer.
1028
ERROR: Field type of buffer does not match routing criteria type
Description
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.
Action
Contact your BEA TUXEDO System Technical Support.
1029
ERROR: Unknown field type used for FML routing
Description
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.
Action
Contact your BEA TUXEDO System Technical Support.
1030
ERROR: Routing field value for 'service' not valid
Description
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.
Action
Make sure the routing field value is valid. Correct the routing criteria in the RANGES value of the UBBCONFIG file.
See Also
ubbconfig(5)
1035
ERROR: Network device not specified
Description
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).
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.
Action
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.
See Also
ubbconfig(5)
1036
ERROR: Bad TLI Call sequence number seq, Will not send disconnect sequence
Description
While accepting a network connection, an error occurred indicating a bad TLI sequence number. In this case, the connection is not explicitly disconnected.
Action
Check that the network is functioning properly.
1037
ERROR: Unable to find view file for type view_name
Description
An attempt to allocate a VIEW typed buffer using tpalloc failed because the description for the view could not be found.
Action
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.
See Also
tpalloc(3c), viewfile(5)
1038
ERROR: Insufficient space allocated for type view_name
Description
An attempt to allocate a VIEW typed buffer using tpalloc failed because the buffer length specified was smaller than the size of the view.
Action
Allocate a larger buffer based on the size of the structure associated with the view.
See Also
tpalloc(3c), viewfile(5)
1039
ERROR: Unable to find view file for type view_name
Description
An attempt to re-allocate a VIEW typed buffer using tprealloc failed because the description for the view could not be found.
Action
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.
See Also
tprealloc(3c), viewfile(5)
1040
ERROR: Insufficient space reallocated for type view_name
Description
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.
Action
Allocate a larger buffer based on the size of the structure associated with the view.
See Also
tprealloc(3c), viewfile(5)
1041
ERROR: Can't find view file for type view_name
Description
An attempt to transmit a VIEW typed buffer failed because the description for the view could not be found.
Action
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.
See Also
viewfile(5)
1042
ERROR: tmroute failed, could not find routing criteria of routing_name for buffer type type subtype view_name
Description
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).
Action
Correct and re-load the UBBCONFIG file or provide an application-specific routing function for VIEW typed buffers.
See Also
typesw(5)
1043
ERROR: Illegal offset value for view_name
Description
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.
Action
Contact your BEA TUXEDO system Technical Support.
1044
ERROR: Routing field for 'routing_field' null
Description
During data-dependent routing for a VIEW buffer, the specified routing_field value in the VIEW buffer was null.
Action
Make sure the routing field is correctly set in the VIEW buffer.
1046
ERROR: Unknown field type used for routing
Description
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.
Action
Contact your BEA TUXEDO system Technical Support.
1047
ERROR: Routing field value for 'service' not valid
Description
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.
Action
Make sure the routing field value is valid. Correct the routing criteria in the RANGES value of the UBBCONFIG file.
See Also
ubbconfig(5)
1048
ERROR: Don't know how to encode/decode data for request opcode 0xopcode
Description
While sending a request, the internal opcode, opcode, was not recognized. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
1049
ERROR: Don't know how to encode/decode data for reply opcode 0xopcode
Description
While receiving a reply, the internal opcode, opcode, was not recognized. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
1050
ERROR: Invalid parameter
Description
One of the internal routines to manage BEA TUXEDO data structures received an invalid parameter. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
1051
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to allocate space for an encryption key.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1052
ERROR: Invalid parameter
Description
One of the internal routines to manage BEA TUXEDO data structures received an invalid parameter. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
1053
ERROR: Invalid parameter
Description
One of the internal routines to manage BEA TUXEDO data structures received an invalid parameter. This should not occur during normal system operation.
Action
Contact your BEA TUXEDO system Technical Support.
1054
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to allocate space for an encryption session key.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1055
ERROR: Invalid parameter
Description
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.
Action
Contact your BEA TUXEDO system Technical Support.
1056
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to allocate space for a session key.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1057
ERROR: Unable to find view file for VIEW32 view_name
Description
An attempt to allocate a VIEW32 typed buffer using tpalloc failed because the description for the view could not be found.
Action
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.
See Also
tpalloc(3c), viewfile(5)
1058
ERROR: Insufficient space allocated for VIEW32 view_name
Description
An attempt to allocate a VIEW32 typed buffer using tpalloc failed because the buffer length specified was smaller than the size of the view.
Action
Allocate a larger buffer based on the size of the structure associated with the view.
See Also
tpalloc(3c), viewfile(5)
1059
ERROR: Unable to find view file for VIEW32 view_name
Description
An attempt to re-allocate a VIEW32 typed buffer using tprealloc failed because the description for the view could not be found.
Action
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.
See Also
tprealloc(3c), viewfile(5)
1060
ERROR: Insufficient space reallocated for VIEW32 view_name
Description
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.
Action
Allocate a larger buffer based on the size of the structure associated with the view.
See Also
tprealloc(3c), viewfile(5)
1061
ERROR: Can't find VIEW32 file for view view_name
Description
An attempt to transmit a VIEW32 typed buffer failed because the description for the view could not be found.
Action
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.
See Also
viewfile(5)
1062
ERROR: Cannot reallocate FML buffer to smaller than its unindexed size
Description
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.
Action
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.
See Also
Finit32(3fml), Fneeded32(3fml), tpalloc32(3c)
1063
ERROR: tmroute failed, could not find routing criteria of routing_name for buffer type FML32
Description
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).
Action
Correct and re-load the UBBCONFIG file or provide an application-specific routing function for FML32 typed buffers.
See Also
typesw(5)
1064
ERROR: Routing field for 'routing_field' null
Description
During data-dependent routing for an FML32 buffer, the specified routing_field value in the FML32 buffer did not exist.
Action
Make sure the routing field is correctly set in the FML32 buffer.
1065
ERROR: Field type of buffer does not match routing criteria type
Description
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.
Action
Contact your BEA TUXEDO system Technical Support.
1066
ERROR: Unknown field type used for FML32 routing
Description
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.
Action
Contact your BEA TUXEDO system Technical Support.
1067
ERROR: Routing field value for 'service' not valid
Description
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.
Action
Make sure the routing field value is valid. Correct the routing criteria in the RANGES value of the UBBCONFIG file.
See Also
ubbconfig(5)
1068
WARN: Could not index FML buffer in postrecv
Description
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.
Action
Either reduce the amount of data stored in the buffer, or use the FML32 buffer type instead.
See Also
Findex(3fml)
1069
WARN: Could not index FML32 buffer in postrecv
Description
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.
Action
Contact your BEA TUXEDO system Technical Support.
See Also
Findex(3fml)
1071
ERROR: Memory allocation failure resynchronizing buffer
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to prepare an FML for transport in _fpresend.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1072
ERROR: Memory allocation failure resynchronizing buffer
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to prepare an FML for transport in _froute.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1073
ERROR: Memory allocation failure resynchronizing FML32 buffer
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to prepare an FML32 for transport in _fpresend32.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1074
ERROR: Memory allocation failure resynchronizing FML32 buffer
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to prepare an FML32 for transport in _froute32.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1075
ERROR: tmroute failed, invalid field identifier for routing criteria routing_name
Description
While converting a routing field to its identifier, the field could not be found.
Action
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.
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), compilation(5), ubbconfig(5)
1076
ERROR: tmroute failed, invalid field identifier for routing criteria routing_name
Description
While converting a routing field to its identifier, the field could not be found.
Action
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.
See Also
BEA TUXEDO Administrator's Guide, tmloadcf(1), compilation(5), ubbconfig(5)
1077
ERROR: Unable to open environment file filename for reading
Description
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.
Action
Verify the specified file name to ensure that the file exists and that the user has read permission on the file.
See Also
ubbconfig(5)
1078
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to process an environment file.
Action
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1079
WARN: Label label not found in environment file
Description
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.
Action
Check that the label value is correct in the environment variable file.
See Also
BEA TUXEDO Administrator's Guide
1080
ERROR: child dup error, rc=rc, errno=errno
Description
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.
Action
The output will not be paginated.
See Also
tmadmin(1), dup(2) in UNIX reference manuals
1081
ERROR: pager: return code 0xrc, errno=errno
Description
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.
Action
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.
See Also
tmadmin(1)
1082
ERROR: could not fork, errno=errno
Description
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.
Action
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.
See Also
tmadmin(1), fork(2) in UNIX reference manuals
1083
ERROR: parent dup error while saving stdout, errno=errno
Description
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.
Action
The output will not be paginated.
See Also
dup(2) in UNIX reference manuals
1084
ERROR: pager: wait status 0xrc, errno=errno
Description
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.
Action
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.
See Also
tmadmin(1), wait(2) in UNIX reference manuals
1085
ERROR: parent dup error for pipe, rc=rc, errno=errno
Description
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.
Action
The output will not be paginated.
See Also
tmadmin(1), dup(2) in UNIX reference manuals
1086
ERROR: restore dup error, rc=rc, errno=errno
Description
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.
Action
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.
See Also
tmadmin(1), dup(2) in UNIX reference manuals
1087
ERROR: could not make pipe, errno=errno
Description
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.
Action
The output will not be paginated. The failure may be due to a limit of file descriptors for programs.
See Also
tmadmin(1), pipe(2) in UNIX reference manuals
1088
ERROR: malloc failed, errno=errno
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while starting the pager process. The pager will not start.
Action
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
Description
Memory allocation failed for retrieving service table entries.
Action
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.
See Also
tpsubscribe(3c)
1090
ERROR: [tpsubscribe - failed to set fieldname field for tpsubscribe message. Ferror32=error]
Description
tpsubscribe(3c) couldn't insert fieldname into FML32 buffer using Fchg32().
Action
Contact your BEA TUXEDO system Technical Support and provide the error.
See Also
tpsubscribe(3c)
1092
ERROR: [tppost - failed to set fieldname field for tppost message]
Description
tppost(3c) couldn't insert fieldname into FML32 buffer using Fchg32().
Action
Contact your BEA TUXEDO system Technical Support.
See Also
tppost(3c), Fchg(3fml)
1093
ERROR: tppost - Can't add field fieldname to FML32 buffer
Description
tppost(3c) couldn't insert fieldname into FML32 buffer using Fchg32().
Action
Contact your BEA TUXEDO system Technical Support.
See Also
tppost(3c), Fchg32(3fml)
1094
ERROR: tpalloc failed. error=error
Description
Memory allocation failed for retrieving service table entries.
Action
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.
See Also
tpalloc(3c)
1095
ERROR: tppost failed when posting event eventname, tperrmsg=<errmsg>, dropping the message
Description
This message indicates that posting of event eventname failed.
Action
Check the error message and take appropriate action.
See Also
tppost(3c)
1096
ERROR: tpunsubscribe - Memory allocation failure
Description
Memory allocation failed for retrieving service table entries.
Action
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.
See Also
tpunsubscribe(3c)
1097
ERROR: [tpunsubscribe - failed to set fieldname field for tpunsubscribe message. Ferror32=error]
Description
tpunsubscribe(3c) couldn't insert fieldname into FML32 buffer using Fchg().
Action
Contact your BEA TUXEDO system Technical Support and provide the error.
See Also
tpunsubscribe(3c)
1098
ERROR: Unexpected TLI return number val
Description
An event was received from the network (using TLI as a provider). The event is not a recognized value.
Action
Contact your BEA TUXEDO system Technical Support.
1099
ERROR: restore dup error, rc=return, errno=errno_val
Description
After completing a pagination operation (from one of the command line interpreters), an error occurred in restoring the standard output.
Action
This may occur if the user interrupts the pager processing or another error occurs with the pager. No action required.
 |
 |
 |