A server entry for servername is configured with the RESTART option but the MAXGEN is set to or defaults to a value less than 2 so that the server will never be restarted.
No action is required. Normally, the MAXGEN value should be set higher so that the server will restart.
ubbconfig (5)
buildserver(1) was parsing the given filename. While parsing the file given via the "-s @filename" option, buildserver encountered a syntax error.
Edit the file specified by the "-s @filename" option. Make sure that each line is a valid argument to the -s option. The file may be commented if the first character of the comment line is "#". Blank lines are also acceptable.
buildserver(1) uses a heap sort algorithm to order the function names. If buildserver(1) was unable to add an element to the heap, then this error will be returned.
If this error occurs consistently, contact BEA TUXEDO System Technical Support.
While buildserver(1) was parsing the -s option, an error occurred. This error could range anywhere from a syntax error to a file input/output error.
Make sure the -s option has the proper syntax. Also make sure that any file specified with the "-s @filename" option exists and has the proper format.
buildserver(1) uses a heap sort in order to manage function names. This error can occur in the second phase of the heap sort if the actual sorted table could not be built.
If this error occurs consistently, then contact the BEA TUXEDO System Technical Support.
The file specified to buildserver(1) via the "-s @filename" option does not exist.
Make sure that the given filename exists. One useful trick is to specify filename as a full path name, rather than a relative path name.
The "-s @filename" option can be used on the command line to buildserver(1). However, the arguments within the file specified by filename cannot specify another file to open and parse. This practice is known as file recursion. File recursion is not supported by buildserver(1).
Remove any lines from filename which begin with the @ character.
While booting the system or updating the MIB, a security file could not be read on the specified machine. Normally, this will occur when security is configured but one or more of the security files have not been populated (for example, SECURITY is set to USER_AUTH but the group and ACL information is not set).
No action is needed if the associated information in not required for the application.
ubbconfig (5)
While booting the system or updating the MIB, a directory needed to hold the security file could not be created.
Verify that the $APPDIR directory exists and has directory permissions that will allow the administrator to create a subdirectory there. Verify that the file system containing $APPDIR has free disk blocks and inodes.
tmboot (1)
While booting the system or updating the MIB, a directory needed to hold the file could not be created.
Verify that the $APPDIR directory exists and that directory permissions will allow the administrator to create a subdirectory there. Verify that the file system containing $APPDIR has free disk blocks and inodes.
tmboot (1)
While booting the system or updating the MIB, a directory needed to hold the file could not be created because a file exists with the same path name.
Remove the file .adm or adm and retry the command.
While booting the system or updating the MIB, the permissions of a directory needed to hold the file could not be changed.
Change ownership of the adm or .adm directory to the administrative UID .
ubbconfig (5) *MACHINES section
While booting the system or updating the MIB, a security file could not be opened for reading or writing.
Verify that the file system containing $APPDIR has free disk blocks and inodes.
While booting the system or updating the MIB, a write failed on a security file being propagated to the specified LMID.
Verify that the file system containing $APPDIR has free disk blocks and inodes.
ubbconfig (5) *MACHINES section
While booting the system or updating the MIB, there was an encryption problem when propagating one of the security files.
Contact your BEA TUXEDO System Technical Support.
While booting the system or updating the MIB, there was an unrecognized return code encountered.
Contact your BEA TUXEDO System Technical Support.
The MAXACLGROUPS parameter in the *RESOURCES section must be greater than 0 and less than 16K. It specifies the maximum number of group identifiers that can be used for ACL permissions checking.
Correct the value of MAXACLGROUPS and re-run tmloadcf(1).
tmloadcf (1)
The MAXACLCACHE parameter in the *MACHINES section must be greater than or equal to 10 and less than 32000. It specifies the number of entries in the cache used for ACL entries when SECURITY is set to ACL or MANDATORY_ACL.
Correct the value of MAXACLCACHE and re-run tmloadcf(1).
tmloadcf (1)
While executing tmloadcf, an attempt to get the current working directory path failed. This can indicate that either the directory pathname is greater than 78 characters in length or that the directory hierarchy is not readable.
Check that the directory hierarchy has the proper permissions and is no longer than 78 characters, and re-execute the command.
The length of the absolute path name of the input file is greater than MAXTLSTRING.
Specify a shorter path name.
In order to run tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1), the security level of the TUXEDO System/T application must be USER_AUTH, ACL, or MANDATORY_ACL.
Change the security level in the ubbconfig(5) file to USER_AUTH, ACL, or MANDATORY_ACL. Run tmloadcf(1) on the new ubbconfig(5) file. Then re-run the command that caused this failure.
In order to run tpusradd(1), tpusrmod(1), or tpusrdel(1), the security level of the TUXEDO System/T application must be USER_AUTH, ACL, or MANDATORY_ACL.
Change the security level in the ubbconfig(5) file to USER_AUTH, ACL, or MANDATORY_ACL. Run tmloadcf(1) on the new ubbconfig(5) file. Then re-run the command that caused this failure.
The client name given to tpacladd(1), tpaclmod(1), or tpacldel(1) was invalid. A client name must not contain the characters ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.
Change the name given to the command in order to comply with the specifications.
The new user name given to tpaclmod(1) or tpacldel(1) was invalid. A user name must not contain the characters '#', ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.
Change the name given to the command in order to comply with the specifications.
An error occurred while compiling a server with the buildserver command. The message prints the exact compilation command.
Check the command that it is valid (e.g., files exist and have the correct permissions). Check the errors generated by the compiler and correct them.
buildserver(1)
Group identifiers must be between 0 and 16383. tpgrpadd(1) or tpgrpmod(1) was presented a group number which is not within these boundaries.
Change the group number to be within the proper boundaries. Re-run the command that caused the error.
Group identifiers must be between 0 and 16383. tpusradd(1) or tpusrmod(1) was presented a group number which is not within these boundaries.
Change the group number to be within the proper boundaries. Re-run the command that caused the error.
The group name given to tpacladd(1), tpaclmod(1), or tpacldel(1) was invalid. A group name must not contain the characters '#', ',', ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.
Change the name given to the command in order to comply with the specifications.
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.
An attempt was made to boot a second primary event server.
An application can only have one primary System Event server and one User Event server. All other event servers must be configured as secondary servers.
TMSYSEVT(5), TMUSREVT(5)
The polling frequency must be a positive value.
The value of polling frequency specified in the UBBCONFIG file for the event server is invalid. Specify a valid value.
TMSYSEVT(5), TMUSREVT(5)
Memory allocation failed for saving control file name.
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.
The TUXEDO System/T server was unable to set FIELDTBLS32 in the process's environment using putenv().
Make the existing environment smaller by unsetting some unneeded variables (or make environment larger if the operating system allows it) and re-start the server.
The TUXDIR environment variable must be set prior to booting a TUXEDO System/T server.
Set the TUXDIR variable and start the server again.
UBBCONFIG (5)
The TUXEDO System/T server was unable to set FIELDTBLDIR32 in the process's environment using putenv().
Make the existing environment smaller by unsetting some unneeded variables (or make environment larger if the operating system allows it) and re-start the server.
The event server couldn't find the FML32 description files.
The event server needs access to $TUXDIR/udataobj/tpadm file and $TUXDIR/udataobj/evt_mib files before it can process any requests. Make sure that the files exists in the directory and are readable by the server.
TMSYSEVT(5), TMUSREVT(5)
The event server couldn't advertise service svc.
The event server couldn't advertise service svc. Make sure that the MAXSERVICES parameter in *RESOURCES section of UBBCONFIG is big enough. If it is not big enough, either change the parameter dynamically or shut down the application and rebuild TUXCONFIG and then reboot the event server.
TMSYSEVT(5), TMUSREVT(5)
The System Event server is gracefully exiting the application.
No action required.
TMSYSEVT (5)
The Event Server couldn't open the static subscription file file.
The Event Server couldn't open the file that lists statically defined subscriptions. Make sure that the file exists. The server uses the default file either if it can't open the specified file or if the file is not specified.
TMSYSEVT(5), TMUSREVT(5)
Memory allocation failed for an FML32 buffer.
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.
The Event Server failed to Finit32() an FML32 buffer.
Contact your BEA TUXEDO System Technical Support and provide the Ferror32 errno.
Finit32 (3)
Reallocation of FML32 buffer to a larger size failed.
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.
The event server failed to parse the control file file.
Check the errstr string in the message and take corrective action. If there are errors associated with the subscriptions in the control file, a bad.PID file is created in APPDIR directory. Correct all the subscriptions that have errors and restart the event server.
Fextread (3)
The event server failed to parse the control file file.
Check the errstr string in the message and take corrective action. If there are errors associated with the subscriptions in the control file, a bad.PID file is created in APPDIR directory. Correct all the subscriptions that have errors and restart the event server.
Fextread(3), EVENT_MIB(5)
The event server failed to parse the control file file.
The event server encountered a UNIX system call error while reading the subscriptions in the control file using the FML32 function Fextread. The errno returned from the system call is specified in the userlog message. Take corrective action and restart the server.
read(2), Fextread(3)
The transaction timeout value specified in the UBBCONFIG file is incorrect.
The transaction timeout value specified in the UBBCONFIG file for Event Server is incorrect. Specify a valid value. The Event Server defaults to 30 seconds for invalid values.
TMSYSEVT(5), TMUSREVT(5)
The transaction timeout value specified in the UBBCONFIG file is too big.
The transaction timeout value specified in the UBBCONFIG file for Event Server is too big. Specify a valid value. The Event Server defaults to 30 seconds for invalid values.
TMSYSEVT(5), TMUSREVT(5)
The Event Server failed to parse the control file file.
The Event Server got an unknown error value from Fextread32(). Check the control file to determine if it is corrupted.
Fextread (3)
The Event Server can't open file for writing subscription records.
The Event Server can't open file for writing subscription records. Check the permissions on the file and restart the server.
A required attribute in a subscription record is missing.
A mandatory attribute in a subscription record is missing. The fieldid of the missing field is in TA_BLDFLD. Correct the error and restart the server to have this subscription take effect.
EVENT_MIB(5), TM_MIB(5)
The FML32 identifier whose fieldid is fldid32 exceeds allowable length.
Correct the length of the field and restart the server to have this subscription take effect.
EVENT_MIB (5)
Only one of the event filters can be specified in a subscription.
You can only specify either TA_EVENT_FILTER or TA_EVENT_FILTER_BINARY in a subscription. Correct the error and resubmit the request.
EVENT_MIB (5)
An invalid value has beed specified for FML32 field fldname32.
The only acceptable values for FML32 field fldname32 are those in values. Specify a valid value and resubmit the request.
EVENT_MIB (5)
Memory allocation failed for Event Server.
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.
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(3), _gp_recomp(3)
Memory allocation failed for saving the control file name.
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.
The Event Server failed to Finit32() an FML32 buffer.
Contact your BEA TUXEDO System Technical Support and provide the Ferror32 errno.
Finit32 (3)
The System Event server is gracefully exiting the application.
No action required.
TMUSREVT (5)
The Event Server couldn't get a field from the FML buffer.
The EVENT API inserts various FML fields into the buffer before dispatching it to the Event Server. This message indicates that the Event Server couldn't get the field out of the FML buffer.
Fget32 (3)
While initializing the Event Server, tpopen() returned an error. The server will not boot.
Use the returned tperrno and check the userlog to determine what the error was. Resolve the problem and re-boot the server.
tpopen(3), TMSYSEVT(5), TMUSREVT(5)
The Event Server received a message from an application program that was sent via tpcall() or tpconnect() instead of tppost(). A failure message is returned to the originator.
Re-write the application software or reconfigure the TUXCONFIG file so that messages are sent to the correct services using the correct primitives.
tppost (3)
The Event Server received a message with an invalid operation code, opcode.
Contact your BEA TUXEDO System Technical Support.
The Event Server received a message from an application program that was sent via tpcall() or tpconnect() instead of tpsubscribe() or tpunsubscribe(). A failure message is returned to the originator.
Re-write the application software or reconfigure the TUXCONFIG file so that messages are sent to the correct services using the correct primitives.
tpsubscribe(3), tpunsubscribe(3), EVENT_MIB(5)
The event server couldn't advertise service svc.
The event server couldn't advertise service svc. Make sure that the MAXSERVICES parameter in *RESOURCES section of UBBCONFIG is big enough. If it is not big enough, either change the parameter dynamically, or shut down the application and rebuild TUXCONFIG and then reboot the event server.
tpadvertise (3)
The Event Server couldn't format the command string before invoking the command.
When the Event Server receives a message due to some client or server posting an event, the data associated with the event is also sent. Then, the Event Server looks up the subscriptions that match this posted event and formats the string as per the subscription before calling system() command. This messages indicates that the formatting failed. Make sure that the Event Server has the required environment variables for the posted data buffer and that the names of the variables in the subscription record are correct.
TMSYSEVT(5), TMUSREVT(5), tpsubscribe(3), tppost(3)
The Event Server couldn't format the command string before invoking the command itself.
When the Event Server receives a message due to some client or server posting an event, the data associated with the event is also sent. Then, the Event Server looks up the subscriptions that match this posted event and formats the string as per the subscription before calling system() command. This messages indicates that the formatting failed. Make sure that the Event Server has the required environment variables for the posted data buffer and that the names of the variables in the subscription record are correct.
TMSYSEVT(5), TMUSREVT(5), tpsubscribe(3), tppost(3)
During Event Server's booting, tpopen() failed which means that Event Server cannot process any notifications in transactional mode.
Check the userlog for the message stating that tpopen() failed for this Event Server. Correct this error and restart the server.
TMSYSEVT(5), TMUSREVT(5), EVENT_MIB(5), tpsubscribe(3), tppost(3)
The Event Server couldn't begin a transaction to do the notifications transactionally.
Make sure that MAXGTT in UBBCONFIG file is big enough for the application needs. If not, increase the value and restart the application.
tpbegin(3), UBBCONFIG(5)
The Event Server failed to abort the transaction it started earlier.
When the Event Server does notifications in transactional mode, it makes one or more tpcall()'s or tpenqueue()'s depending upon the subscriptions that matched the posted event. If any of the calls fail, the server aborts the transaction. This message indicates that tpabort() failed. Check the error string and take corrective action.
tpbegin(3), UBBCONFIG(5)
The Event Server failed to abort the transaction it started earlier.
When the Event Server does notifications in transactional mode, it makes one or more tpcall()'s or tpenqueue()'s depending upon the subscriptions that matched the posted event. If any of the calls fail, the server aborts the transaction. This message indicates that tpabort() failed. Check the error string and take corrective action.
tpabort (3)
The Event Server failed to abort the transaction it started earlier.
When the Event Server does notifications in transactional mode, it makes one or more tpcall()'s or tpenqueue()'s depending upon the subscriptions that matched the posted event. If any of the calls fail, the server aborts the transaction. This message indicates that tpabort() failed. Check the error string and take corrective action.
tpbegin(3), UBBCONFIG(5)
The Event Server failed to commit the transaction it started earlier.
When the Event Server does notifications in transactional mode, it makes one or more tpcall()'s or tpenqueue()'s depending upon the subscriptions that matched the posted event. If all of the requests complete successfully, the server commits the transaction. This message indicates that tpcommit() failed. Check the error string and take corrective action.
tpcommit (3)
The Event Server made a tpcall() on behalf of a subscription due to a posted event.
This message indicates that a posted event eventname resulted in a service call to svc and it failed with tperrno tperrno. Check the message and take corrective action. If this is a non-persistent subscription, the subscription will be removed. So, you may have to resubscribe to that event before this condition can be reproduced.
tpacall (3)
The Event Server made a tpenqueue() on behalf of a subscription due to a posted event.
This message indicates that a posted event eventname resulted in enqueuing a message to queue name qname and it failed with tperrno tperrno. Check the message and take corrective action. If this is a non-persistent subscription, the subscription will be removed. So, you may have to resubscribe to that event before this condition can be reproduced.
tpenqueue (3)
Memory allocation failed for receiving reply message.
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.
The Event Server made a tpacall() on behalf of a subscription due to a posted event. Then, it tried to get the reply for the service call.
This message indicates that a posted event eventname resulted in a service call to svc. When trying to get a reply, it failed with tperrno tperrno. Check the message and take corrective action. If this is a non-persistent subscription, the subscription will be removed. So, you may have to resubscribe to that event before this condition can be reproduced.
tpgetrply (3)
tmloadcf was run on an ASCII configuration file originally created using tmunloadcf in which the internally generated *MIBPERMS section has been modified by the user.
If you have not yet destroyed your previous TUXCONFIG file, it may be unloaded again using tmunloadcf to get a valid ASCII image of the configuration file. You may then edit that image, but be certain not to change the *MIBPERMS section if one exists. If the previous TUXCONFIG file has been destroyed, then you can delete the *MIBPERMS section in its entirety and rerun tmloadcf to regenerate the TUXCONFIG file; however, all application customized permissions for /AdminAPI access will be lost using this method. Alternatively, you can reorder the entries in the *MIBPERMS section using the field name as the primary sort key and the field identifier as the secondary key before rerunning tmloadcf.
tmloadcf (1), tmunloadcf (1), MIB (5)
While posting a system event, a MIB GET call to tpadmcall to retrieve associated information for the event failed. Additional information is printed indicating the cause of the failure.
Check the reason for the failure. No action required.
TM_MIB(5)
The secondary event server couldn't open file file for writing the subscription database it got from the primary event server.
Make sure that the server can create the file file and that there are enough inodes in the file system.
TMSYSEVT(5), TMUSREVT(5)
The Event Server failed to Finit32() an FML32 buffer.
Contact your BEA TUXEDO System Technical Support and provide the Ferror32 errno.
Finit32 (3)
The event server failed to write a subscription record in the file file.
Make sure that the control file is not inadvertently deleted while the server is running. Check the Ferror32 Ferror32 in the message and take corrective action.
Ffprint32 (3)
The secondary server made a tpcall() to primary event server to get a new copy of the subscription database. This message states that the call failed.
Check the error string errstr in the message and take corrective action.
TMSYSEVT(5), TMUSREVT(5)
The primary event server couldn't unload the subscription database into a file.
The primary event server updates the control file whenever a client/server unsubscribes to a subscription or if the event server garbage-collects stale subscriptions. This message indicates that the server failed to write the new database to the file. Check for other messages preceding this message and take corrective action.
TMSYSEVT(5), TMUSREVT(5)
The primary event server can't add CURSID to FML buffer.
The primary server uses a sequence number to generate subscription handles. When a secondary event server queries the primary for a new copy of the subscription database, this sequence number is also sent with it. Later on, when the secondary queries again, this sequence number is used to determine if a new copy of the subscription database needs to be sent or not. This message indicates that the primary server couldn't set the sequence number in the FML buffer. Contact your BEA TUXEDO System Technical Support and provide the Ferror errno.
Fchg (3)
The primary event server failed to allocate a CARRAY buffer.
If the userlog message preceding this message states that it is out of memory, then add more memory to the system or configure the system to allow more virtual memory for the processes. If the tperrno tperrno is anything else, contact your BEA TUXEDO System Technical Support and provide the tperrno.
tpalloc (3)
Contact your BEA TUXEDO System Technical Support.
Contact your BEA TUXEDO System Technical Support.
The primary event server failed to allocate an FML buffer.
If the userlog message preceding this message states that it is out of memory, then add more memory to the system or configure the system to allow more virtual memory for the processes. If the tperrno tperrno is anything else, contact your BEA TUXEDO System Technical Support and provide the tperrno.
tpalloc(3)
The secondary event server can't add CURSID to FML buffer.
When the secondary event server polls the primary server for subscription database, it sends the sequence number it received previously from the primary server. This message states that the secondary server couldn't insert the sequence number field to FML buffer. Contact your BEA TUXEDO System Technical Support and provide the Ferror errno.
Fchg (3)
The secondary event server can't add CURSOC to FML buffer.
When the secondary event server polls the primary server for subscription database, it sends its poll interval. This message states that the secondary server couldn't insert the poll interval field to FML buffer. Contact your BEA TUXEDO System Technical Support and provide the Ferror errno.
Fchg (3)
The secondary event server can't get CURSID from FML buffer.
When the secondary event server polls the primary server for subscription database, the primary server sends its sequence number back to the secondary server. This message states that the secondary server couldn't extract the sequence number field from the FML buffer. Contact your BEA TUXEDO System Technical Support and provide the Ferror errno.
Fget (3)
When the secondary event server receives a new copy of subscription database, it first deletes the old subscription records and then adds the new records into memory. This message indicates that it could not delete the old database.
Contact your BEA TUXEDO System Technical Support.
The secondary event server failed to allocate a CARRAY buffer.
If the userlog message preceding this message states that it is out of memory, then add more memory to the system or configure the system to allow more virtual memory for the processes. If the tperrno tperrno is anything else, contact your BEA TUXEDO System Technical Support and provide the tperrno.
tpalloc (3)
Contact your BEA TUXEDO System Technical Support.
Contact your BEA TUXEDO System Technical Support.
After the secondary event server receives a copy of the subscription database from the primary, it first loads into a file file and then starts parsing the file to load it into memory. This message states that it couldn't write to the file.
Check the errno errno and take corrective action. Make sure that the directory is writable and that there is enough space in the file system.
Fwrite (3)
After the secondary event server receives a copy of the subscription database from the primary, it first loads into a temporary file file and then starts parsing the file to load it into memory. After parsing the file, it links the temporary file to the control file. This message states that link() failed with errno errno.
Check the errno errno and take corrective action. Make sure that the directory is writable and that there is enough space in the file system.
After the secondary event server receives a copy of the subscription database from the primary, it first loads into a temporary file file and then starts parsing the file to load it into memory. After parsing the file, it links the temporary file to the control file. After linking the file, it deletes the temporary file. This message states that unlink() failed with errno errno.
Check the errno errno and take corrective action. Make sure that the directory is writable and that there is enough space in the file system.
unlink (2)
The secondary event server failed to parse the control file file.
Make sure that the file file was not inadvertently deleted while the server is running. Also, check for userlog messages preceding this message for a more descriptive message.
TMSYSEVT(5), TMUSREVT(5)
The primary event server can't add CURSID to FML buffer.
The primary server uses a sequence number to generate subscription handles. When a secondary event server queries the primary for a new copy of the subscription database, this sequence number is also sent with it. Later on, when the secondary queries again, this sequence number is used to determine if a new copy of the subscription database needs to be sent or not. This message indicates that the primary server couldn't set the sequence number in the FML buffer. Contact your BEA TUXEDO System Technical Support and provide the Ferror errno.
Fchg(3), TMSYSEVT(5), TMUSREVT(5)
The secondary event server can't get CURSID from FML buffer.
When the secondary event server polls the primary server for the subscription database, the primary server sends its sequence number back to the secondary server. This message states that the secondary server couldn't extract the sequence number field from the FML buffer. Contact your BEA TUXEDO System Technical Support and provide the Ferror errno.
Fget(3), TMSYSEVT(5), TMUSREVT(5)
After the secondary event server receives a copy of the subscription database from the primary, it first loads into a temporary file file and then starts parsing the file to load it into memory. After parsing the file, it links (renames) the temporary file to the control file. This message states that link() failed with errno errno.
Check the errno errno and take corrective action. Make sure that the directory is writable and that there is enough space in the file system.
Each group specified by the -g argument of tpacladd(1) or tpaclmod(1) must be greater than 0 characters and less than 31 characters.
Modify the -g argument so that the group identification falls within acceptable limits.
Each group specified by the -g argument of tpacladd(1) or tpaclmod(1) must be greater than 0 characters and less than 31 characters.
Modify the -g argument so that the group identification falls within acceptable limits.
When tpacladd(1) or tpaclmod(1) was attempting to retrieve information about one of the groups specified by the -g argument, an error occurred.
Try the command again. If it fails consistently, then contact your BEA TUXEDO System Technical Support.
tpacladd(1) or tpaclmod(1) encountered a group number given via the -g parameter which does not exist.
Add the desired group to the T_ACLGROUP MIB by using the tpgrpadd(1) command, and then re-run this command.
tpacladd(1) or tpaclmod(1) encountered a group name given via the -g parameter which does not exist.
Add the desired group to the T_ACLGROUP MIB by using the tpgrpadd(1) command, and then re-run this command.
The type field given via the -t option to tpacladd(1), tpaclmod(1), or tpacldel(1) was invalid. The only recognized types are SERVICE, ENQ, DEQ, or POSTEVENT.
Change the -t option of the command being run to SERVICE, ENQ, DEQ, or POSTEVENT.
The name given to tpacladd(1), tpaclmod(1), or tpacldel(1) was invalid. An ACL name must not contain the characters '#', ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.
Change the name given to the command in order to comply with the specifications.
When adding or deleting a field from an FML buffer, the given error occurred. This error occurs when running tpacladd(1), tpaclmod(1), or tpacldel(1).
Try running the command again. If it fails consistently, contact your TUXEDO System Technical Support.
When using the command tpacladd(1), tpaclmod(1), or tpacldel(1), the system ran out of memory.
Check the memory on the system where the command was run. If it seems that there should be enough memory for this operation, contact your TUXEDO System Technical Support.
tpacladd(1), tpaclmod(1), and tpacldel(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the TUXEDO System/T configuration file.
Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
The given executable name is not known. This error can happen if the tpgrpadd(1), tpgrpdel(1), or tpgrpmod(1) commands have been renamed.
Do not rename the tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1) commands. Use the original names with which the TUXEDO System binary was packaged.
When running the tpacladd(1), tpaclmod(1), or tpacldel(1) command, an error occurred in the MIB(5). The returned error number was retrieved from the TA_ERROR field of the returned FML32 buffer.
Consult the MIB(5) manual pages to determine exactly which error was returned. Further action may be suggested by the nature of the error returned by the MIB.
The group name given to tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1) was invalid. A group name must not contain the characters '#', ',', ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.
Change the group name given to the command in order to comply with the specifications.
When running the tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1) command, an error occurred in the MIB(5). The returned error number was retrieved from the TA_ERROR field of the returned FML32 buffer.
Consult the MIB(5) manual pages to determine exactly which error was returned. Further action may be suggested by the nature of the error returned by the MIB.
When adding or deleting a field from an FML32 buffer, the given error occurred. This error occurs when running tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1).
Try running the command again. If it continues to fail, contact your TUXEDO System Technical Support.
When using the commands tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1), the system ran out of memory.
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.
When running the tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1) command, an error occurred in the MIB(5). The returned error number was retrieved from the TA_ERROR field of the returned FML32 buffer.
Consult the MIB(5) manual pages to determine exactly which error was returned. Further action may be suggested by the nature of the error returned by the MIB.
tpgrpadd(1), tpgrpmod(1), and tpgrpdel(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the TUXEDO System/T configuration file.
Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
The new group name given to tpgrpmod(1) was invalid. A group name must not contain the characters '#', ',', ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.
Change the new group name given to the command in order to comply with the specifications.
When tpgrpadd(1) or tpgrpmod(1) was attempting to retrieve information about groups specified on the command line, an error occurred.
Try the command again. If the command fails consistently, then contact your BEA TUXEDO System Technical Support.
In the T_ACLGROUP class, no two groups can have the same name. tpgrpmod(1) attempted to add two groups with the same name.
Do not attempt to have two groups with the same name. Change the group name and re-run the command.
tpgrpmod(1) attempted to modify a group that does not exist.
Use tpgrpadd(1) to add new groups to the T_ACLGROUP class. Use the TUXEDO System GUI to get a complete list of the currently defined groups.
When adding or deleting a field from an FML32 buffer, the given error occurred. This error occurs when running tpusradd(1), tpusrmod(1), or tpusrdel(1).
Try running the command again. If it fails again, contact your TUXEDO System Technical Support.
When using the commands tpusradd(1), tpusrmod(1), or tpusrdel(1), the system ran out of memory.
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.
When tpusradd(1) or tpusrmod(1) was attempting to retrieve information about a group specified on the command line, an error occurred.
Try the command again. If it fails consistently, then contact your BEA TUXEDO System Technical Support.
tpusradd(1) or tpusrmod(1) encountered a group number given via the -g parameter which does not exist.
Add the desired group to the T_ACLGROUP MIB by using the tpgrpadd(1) command, and then re-run this command.
tpusradd(1) or tpusrmod(1) encountered a group name given via the -g parameter which does not exist.
Add the desired group to the T_ACLGROUP MIB by using the tpgrpadd(1) command, and then re-run this command.
The given executable name is not known. This error can happen if the tpusradd(1), tpusrdel(1), or tpusrmod(1) commands have been renamed.
Do not rename the tpusradd(1), tpusrmod(1), or tpusrdel(1) commands. Use the original names with which the TUXEDO System binary was packaged.
tpusradd(1), tpusrmod(1), and tpusrdel(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the TUXEDO System configuration file.
Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
In order to run tpacladd(1), tpaclmod(1), or tpacldel(1), the security level of the TUXEDO System/T application must be USER_AUTH, ACL, or MANDATORY_ACL.
Change the security level in the ubbconfig(5) file to USER_AUTH, ACL, or MANDATORY_ACL. Run tmloadcf(1) on the new ubbconfig(5) file. Then re-run the command that caused this failure.
In the T_ACLPRINCIPAL class, no two users can have the same numeric identification. tpusrmod(1) attempted to add two users with the same identification.
Do not attempt to have two users with the same numeric identification. Change the user name and re-run the command.
tpusrmod(1) attempted to modify a user which does not exist.
Use tpusradd(1) to add new users to the T_ACLPRINCIPAL class. Use the TUXEDO System GUI to get a complete list of the currently defined users.
The user name given to tpusradd(1), tpusrmod(1), or tpusrdel(1) was invalid. A user name must not contain the characters '#', ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.
Change the name given to the command in order to comply with the specifications.
The group name given to tpusradd(1) or tpusrmod(1) was invalid. Either the group did not exist or there was a syntax error in the group name.
Use tpgrpadd(1) to add new groups. Change the group name given to the command to correspond to an existing group. Change the group name to conform to the specifications for group names.
User numbers in the T_ACLPRINCIPAL class must be between 1 and 131071. A user number presented to tpusradd(1) or tpusrmod(1) was not within that range.
Change the user number to be within the allowable range and re-run the command.
When running the tpusradd(1), tpusrmod(1), or tpusrdel(1) command, an error occurred in the MIB(5). The returned error number was retrieved from the TA_ERROR field of the returned FML32 buffer.
Consult the MIB(5) manual pages to determine exactly which error was returned. Further action may be suggested by the nature of the error returned by the MIB.
In the T_ACLGROUP MIB, no two groups can have the same numeric identification. tpgrpadd(1) or tpgrpmod(1) attempted to add two groups with the same identification.
Do not attempt to have two groups with the same numeric identification. Change the identification number and re-run the command.
In the T_ACLPRINCIPAL class, no two users can have the same numeric identification. tpusradd(1) or tpusrmod(1) attempted to add two users with the same identification.
Do not attempt to have two users with the same numeric identification. Change the identification number and re-run the command.
Due to an error processing the user password, this user has not been added to the system. This can happen when using tpusradd(1) or tpusrmod(1).
Re-run the command that caused the error. If this error occurs consistently, call TUXEDO System Technical Support.
The user passwords entered to tpusradd(1) or tpusrmod(1) do not match.
Re-run the command and make sure that you enter the passwords correctly each time you are prompted.
tpusradd(1), tpusrmod(1), or tpusrdel(1) was unable to retrieve the user identification from the host system.
Make sure that the user id of the TUXEDO System administrator is known to the system. If the user id is known to the system, then contact your TUXEDO System Technical Support.
tpacladd(1), tpaclmod(1), or tpacldel(1) was unable to retrieve the user identification from the host system.
Make sure that the user id of the TUXEDO System administrator is known to the system. If the user id is known to the system, then contact your TUXEDO System Technical Support.
tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1) was unable to retrieve the user identification from the host system.
Make sure that the user id of the TUXEDO System administrator is known to the system. If the user id is known to the system, then contact your BEA TUXEDO System Technical Support.
This message states that the specified machine changed to ACTIVE. A complete listing of the current parameters are sent along in the posted buffer.
This is an informational message.
EVENT_MIB (5), TM_MIB (5)
The given executable name is not known. This error can happen if the tpacladd(1), tpacldel(1), or tpaclmod(1) commands have been renamed.
Do not rename the tpacladd(1), tpaclmod(1), or tpacldel(1) commands. Use the original names with which the TUXEDO System binary was packaged.
When running the tpusradd(1), tpusrmod(1), or tpusrdel(1) command, an error occurred in the MIB(5). The returned error number was retrieved from the TA_ERROR field of the returned FML32 buffer.
Consult the MIB(5) manual pages to determine exactly which error was returned. Further action may be suggested by the nature of the error returned by the MIB.
This message indicates that the virtual circuit between machines LMID1 and LMID2 changed to an INACTIVE state. A complete listing of the current parameters are sent along in the posted buffer.
This is an informational message.
EVENT_MIB (5), TM_MIB (5)
This message states that the specified machine changed to a new state as mentioned in the message. A complete listing of the current parameters are sent along in the posted buffer.
This is an informational message.
EVENT_MIB (5), TM_MIB (5)
This message indicates that the virtual circuit between machines LMID1 and LMID2 changed to a new state as mentioned in the message. A complete listing of the current parameters are sent along in the posted buffer.
This is an informational message.
EVENT_MIB (5), TM_MIB (5)
This message indicates that the virtual circuit between machines LMID1 and LMID2 changed to a SUSPENDED state. A complete listing of the current parameters are sent along in the posted buffer.
This is an informational message.
EVENT_MIB (5), TM_MIB (5)
This message indicates that the server specified above changed to a new state. A complete listing of the server attributes are sent in the posted buffer.
This is an informational message.
EVENT_MIB (5), TM_MIB (5)
This message indicates that the client specified above changed to a new state. A complete listing of the current attributes of the client are sent in the posted buffer.
This is an informational message.
EVENT_MIB (5), TM_MIB (5)
tpacladd(1), tpaclmod(1), and tpacldel(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the TUXEDO System/T configuration file.
Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
tpgrpadd(1), tpgrpmod(1), and tpgrpdel(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the TUXEDO System/T configuration file.
Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
tpusradd(1), tpusrmod(1), and tpusrdel(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the TUXEDO System/T configuration file.
Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
This message indicates that the network link between the two machines specified changed to a new state. A complete listing of the current parameters are sent along in the posted buffer.
This is an informational message.
EVENT_MIB (5), TM_MIB (5)
This message states that the specified machine changed to an INACTIVE state. A complete listing of the current parameters are sent along in the posted buffer.
This is an informational message.
EVENT_MIB (5), TM_MIB (5)
This message indicates that the event server failed to perform at least one notification for a posted event.
Check to make sure that the notifications specified in the subscriptions that match the posted events can be done.
EVENT_MIB (5), TM_MIB (5)
The system event server periodically sends a message to itself to detect blocking conditions on the message queues. This event is generated if the server can't put a message on the queue in no-block node. It can also be generated if the received message doesn't match what was sent out earlier. The second case will probably never happen.
Configure larger message queues or distribute the load in the application equally among all the machines.
EVENT_MIB (5), TM_MIB (5)
Memory allocation failed in the event server.
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.
The event server periodically tests the message queue subsystem for blocking conditions by sending a message to itself in NOWAIT mode and receiving the message right after. This message indicates that the received message didn't match the sent message.
Contact your BEA TUXEDO System Technical Support.
TMSYSEVT(5), TMUSREVT(5)
When adding or deleting a field from an FML32 buffer, the given error occurred. This error occurs when running tpaclcvt(1).
Try running the command again. If it fails consistently, contact your TUXEDO System Technical Support.
When using the command tpaclcvt(1), the system ran out of memory.
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.
The given line number in the user file was ignored by tpaclcvt(1). The line was not formatted correctly, and hence was ignored.
Be sure that the file which is being converting has the correct format.
If tpaclcvt(1) encounters a user identification number which is not numeric, then it does not attempt to add the user. This can occur when converting the user file.
Be sure that the file which is being converted has the correct format.
User identification numbers are only valid within the range 1 to 131,071. If tpaclcvt(1) encounters a user identification number which is not in the given range, then it does not attempt to add the user.
Any users which tpaclcvt(1) could not add can be added with tpusradd(1).
If tpaclcvt(1) encounters a group identification number which is not numeric, then it does not attempt to add the user. This can occur when converting the user file.
Any users which tpaclcvt(1) could not add can be added with tpusradd(1).
The given line in the user file was not converted by tpaclcvt(1). This is because a # character was encountered in the username, which is illegal.
Any users which tpaclcvt(1) could not add can be added with tpusradd(1).
tpaclcvt(1) encountered an error when attempting to get information concerning the user on the given line.
Examine the error code returned. This error can be used to determine the actual TUXEDO System error that occurred.
When tpaclcvt(1) is converting a user file, it attempts to look for duplicate users. If an error occurs while extracting the number of users, this message occurs.
Any users which tpaclcvt(1) could not add can be added with tpusradd(1).
Any users which tpaclcvt(1) could not add can be added with tpusradd(1).
You can add any user which tpaclcvt(1) did not add with tpusradd(1).
tpaclcvt(1) encountered an error when attempting to get information concerning user identifiers.
Examine the error code returned. This error can be used to determine the actual TUXEDO System error that occurred.
When tpaclcvt(1) is converting a user file, it attempts to look for duplicate users identification numbers. If an error occurs while extracting the number of user identifiers, this message occurs.
Any users which tpaclcvt(1) could not add can be added with tpusradd(1).
tpaclcvt(1) did not add the given user because that user identification number already exists.
Any users which tpaclcvt(1) could not add can be added with tpusradd(1).
tpaclcvt(1) was attempting to modify the user file to add the given user.
Run a diagnostic on the disk to see whether the disk is corrupted. If it is corrupted, buy a new disk and run the command again. If it is not, then contact BEA TUXEDO System Technical Support.
The given line number in the group file was ignored by tpaclcvt(1). The line was not formatted correctly, and hence was ignored.
Be sure that the file which is being converted has the correct format.
If tpaclcvt(1) encounters a group identification number that is not numeric, then it does not attempt to add the user. This can occur when converting the group file.
Any groups which tpaclcvt(1) could not add can be added with tpgrpadd(1).
tpaclcvt(1) encountered an error when attempting to add a group. The error string can help to determine exactly what error occurred.
Examine the error code returned. This error can be used to determine the actual TUXEDO System error that occurred.
tpaclcvt(1) encountered an error when adding a group to the T_ACLGROUP class. When attempting to retrieve the error from the returned FML32 buffer, an error occurred.
If this error occurs consistently, then contact BEA TUXEDO System Technical Support.
tpaclcvt(1) received the given error string from the MIB when adding the group on the given line.
Use the error string returned from the MIB to determine exactly what error occurred.
tpaclcvt(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the TUXEDO System/T configuration file.
Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
tpaclcvt(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the TUXEDO System/T configuration file.
Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
tpaclcvt(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the TUXEDO System/T configuration file.
Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
tpaclcvt(1) must be run on a system that is not booted.
Bring the TUXEDO System down using tmshutdown(1). Then re-run this command.
tpaclcvt(1) is converting the given group file.
Be patient.
tpaclcvt(1) could not find the group file to be converted.
Be sure the name of the file to be converted is correct and that this file exists. Re-run the command.
tpaclcvt(1) is converting the given user file.
Be patient.
tpaclcvt(1) could not find the user file to be converted.
Be sure the name of the file to be converted is correct and that this file exists. Re-run the command.
tpaclcvt(1) could not create the ACL user file.
There are several kernel parameters which could cause this error. Two obvious ones include the maximum allowed size for files and the number of allowable open file descriptors. Disk space could also be a problem. Increase the appropriate kernel parameters or buy a new disk, then try the command again.
When tpaclcvt(1) was attempting to get information about the current TUXEDO System/T configuration, an unexpected error occurred.
Make sure your TUXCONFIG variable is set correctly and that your TUXEDO System/T configuration file is valid. If the command continues to return this error, call TUXEDO System Technical Support.
tpacladd(1), tpaclmod(1), and tpacldel(1) can only be run by the TUXEDO System system administrator.
Log into the system as the TUXEDO System/T administrator and re-run this command.
tpgrpadd(1), tpgrpmod(1), and tpgrpdel(1) can only be run by the TUXEDO System system administrator.
Log into the system as the TUXEDO System/T administrator and re-run this command.
tpusradd(1), tpusrmod(1), and tpusrdel(1) can only be run by the TUXEDO System system administrator.
Log into the system as the TUXEDO System/T administrator and re-run this command.
tpaclcvt(1) can only be run by the TUXEDO System/T system administrator.
Log into the system as the TUXEDO System/T system administrator and re-run this command.
Under TUXEDO System/T system security, user identification numbers of -1 were valid. However, the ACL users cannot have -1 as a user identification number. When converting a user file using tpaclcvt(1), user identification numbers of -1 are mapped to valid user identification numbers.
In order to specify particular user identification numbers, use tpusrmod(1).
User identification numbers are only valid within the range 1 to 131,071. If tpaclcvt(1) cannot generate a unique number within this range, then no more users can be added to the system.
Delete users before calling tpaclcvt(1).
The event server failed to allocate memory for an FML32 buffer.
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 (3)
The event server couldn't call svc svc.
The event server periodically garbage collects stale subscriptions of clients that terminated without unsubscribing. It makes a call to svc to determine if a client is alive. This message states that the service call failed.
TM_MIB(5), TMSYSEVT(5), TMUSREVT(5)
The TUXEDO System supplied AUTHSVR failed because the SECURITY parameter in the ubbconfig(5) file was set to NONE or APP_PW. In order for the AUTHSVR to properly authorize users, the SECURITY parameter must be set to USER_AUTH, ACL, or MANDATORY_ACL.
Change the SECURITY setting in the ubbconfig(5) file to USER_AUTH, ACL, or MANDATORY_ACL. Run tmloadcf(1) on the new ubbconfig file and boot the system again.
ACL and MANDATORY_ACL have a fixed authentication file name relative to the APPDIR of the machine. However, the -f option to AUTHSVR specified a different filename while authentication was ACL or MANDATORY_ACL. This is an error which will cause AUTHSVR to fail.
Change the CLOPT line of the AUTHSVR to remove the -f option. The appropriate authentication file will be used by default. Reboot the AUTHSVR.
AUTHSVR attempts to advertise AUTHSVC if the authentication level is USER_AUTH. If an error occurs when attempting to advertise this service, then this error is returned.
Increase the MAXSERVICES parameter in the ubbconfig(5) file. Run tmloadcf(1) on the new file. Reboot the application. If this error occurs consistently, contact BEA TUXEDO System Technical Support.
The AUTHSVR is terminating normally.
No action required.
The given username/clientname attempted to log into the TUXEDO System and was denied access by the AUTHSVR.
Do whatever is appropriate for attempted security break-ins in the TUXEDO System/T System application.
The wildcard character "*" was presented as either the username or clientname in the TPINIT buffer.
If wildcard characters are appropriate for the security scheme to which your application adheres, then this warning can be ignored. Otherwise, do whatever is appropriate in the security scheme of your TUXEDO System application.
When generating the cache which the AUTHSVR uses to authenticate users, a duplicate entry was found in the authentication file.
Use tpusradd(1), tpusrmod(1), and tpusrdel(1) to maintain the user password files. NEVER edit these files manually.
AUTHSVR could not open the given password file. This file may have been removed accidentally or may have been renamed.
If the password file cannot be found, then it is assumed that there are no users in the TUXEDO System. When users are added via tpusradd(1), then the password file will be created and this error will no longer appear.
AUTHSVR could not allocate memory.
Make sure enough memory exists on the system running the AUTHSVR. If it appears that there should be enough memory to run AUTHSVR, and this error happens consistently, then contact the BEA TUXEDO System Technical Support.
The event server couldn't open file file for writing the subscription database.
The event server writes a new copy of the subscription database in the temporary file file. Then, it links this file to the control file specified in the UBBCONFIG file. This message indicates that the server couldn't open the temporary file for writing. Check the file system parameters and take corrective action.
This message indicates that the server specified above died abnormally and the BBL detected this condition in its periodic scan of the BB.
Debug the server and fix the problem before it is restarted again.
EVENT_MIB (5), TM_MIB (5)
A TMIB request to change the state of a group, name, to a new state, newstate its associated machine lmid completed successfully.
No action required.
TM_MIB(5)
The event server appends new subscriptions to the end of the control file. This message states that the control file file was inadvertently removed while the server is running.
Prevent such errors from happening by protecting the APPDIR directory. Since this file serves as a backup copy of subscriptions in an application running only a primary event server, it is important that this file be protected.
Under the authentication level USER_AUTH, if the AUTHSVR cannot find the user file relative to APPDIR, then it attempts to use /etc/passwd for authentication. If AUTHSVR cannot find the /etc/passwd file, it fails.
Make sure that either the user file relative to APPDIR has been created using tpusradd(1) or that the /etc/passwd file is readable by the TUXEDO System administrator.
An attempt was made to subscribe to an entry that matches one in the event server's list.
Check the tpsubscribe(3) and EVENT_MIB(5) man pages for more detailed explanation.
tpsubscribe(3), EVENT_MIB(5)
The event server failed to perform Fchg32() on an FML32 buffer.
Contact your BEA TUXEDO System Technical Support and provide the Ferror32 Ferror32.
The event server failed to perform Fchg32() on an FML32 buffer.
Contact your BEA TUXEDO System Technical Support and provide the Ferror32 Ferror32.
The event server failed to perform Fchg32() on an FML32 buffer.
Contact your BEA TUXEDO System Technical Support and provide the Ferror32 Ferror32.
The event server failed to perform Fchg32() on an FML32 buffer.
Contact your BEA TUXEDO System Technical Support and provide the Ferror32 Ferror32.
The event server failed to perform Fchg32() on an FML32 buffer.
Contact your BEA TUXEDO System Technical Support and provide the Ferror32 Ferror32.
If the notification mechanism selected for a subscription is to place a message in a TUXEDO System reliable queue, then TA_QCTL_DEQ_TIME must be specified if TA_QCTL_QTIME_ABS is chosen.
Correct the error and re-issue the subscription.
tpsubscribe(3), tpenqueue(3), EVENT_MIB(5)
If the notification mechanism selected for a subscription is to place a message in a TUXEDO System reliable queue, then either TA_QCTL_QTIME_ABS or TA_QCTL_QTIME_REL can be chosen.
Correct the error and re-issue the subscription.
tpsubscribe(3), tpenqueue(3), EVENT_MIB(5)
If the notification mechanism selected for a subscription is to place a message in a TUXEDO System reliable queue, then TA_QCTL_DEQ_TIME must be specified if TA_QCTL_QTIME_REL is chosen.
Correct the error and re-issue the subscription.
tpsubscribe(3), tpenqueue(3), EVENT_MIB(5)
If the notification mechanism selected for a subscription is to place a message in a TUXEDO System reliable queue, then TA_QCTL_PRIORITY must be in a valid range.
Correct the error and re-issue the subscription.
tpsubscribe(3), tpenqueue(3), EVENT_MIB(5)
An attempt was made to do a GET operation on one of the EVENT_MIB classes, and no records match the specified criteria.
Correct the error and re-issue the subscription.
EVENT_MIB (5)
The event server couldn't translate the user-supplied FML32 buffer into a view representation. This can occur either due to view description files being inadvertently deleted or due to internal system error.
If no view description files have been deleted from the TUXDIR tree, contact your BEA TUXEDO System Technical Support.
EVENT_MIB (5)
The event server received a request for subscribe/unsubscribe directly without either calling tpsubscribe()/tpunsubscribe() or making a MIB request to .TMIB service.
You can subscribe/unsubscribe by using using EVENT API or EVENT_MIB. Correct the error and re-issue the request.
EVENT_MIB (5)
Memory allocation failed for an FML32 buffer.
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.
The event server received a request for subscribe/unsubscribe directly without either calling tpsubscribe()/tpunsubscribe() or making a MIB request to .TMIB service.
You can subscribe/unsubscribe by using using EVENT API or EVENT_MIB. Correct the error and re-issue the request.
tpsubscribe(3), TM_MIB(5), EVENT_MIB(5)
The event server couldn't open the control file for truncating the contents. When there are no active subscriptions in-memory, the control file is automatically truncated to reflect the current state.
This message implies that the control file may have been inadvertently deleted while the event server is running. The control file cannot be removed while the event server is running.
An attempt to initialize the networking software from the BRIDGE failed.
Make sure that the correct networking software is installed on the system and that the network is accessible.
tmunloadcf was run with an undocumented administrative option.
Re-run the command without the -o option, or contact your TUXEDO System/T Technical Support if you think that you need this option.
tmunloadcf(1)
tmunloadcf failed to open the name filename. The associated system error is printed.
Check that there is space in the file system associated with filename and re-run the command.
tmunloadcf(1)
The full pathname for the current directory in which tmunloadcf is being run is longer than 256 characters.
Change the directory structure such that the pathname is less than 256 characters, and re-run the command.
The full pathname for a file generated by tmunloadcf is longer than 256 characters.
Change the directory structure such that the pathname is less than 256 characters, and re-run the command.
An attempt to initialize the networking software while trying to access the tagent failed. This could be in any of the administrative processes including the BBL, DBBL, or BRIDGE (as indicated by the userlog message).
Make sure that the correct networking software is installed on the system and that the network is accessible.
An attempt to initialize the networking software from tlisten (the TUXEDO System network listener) failed.
Make sure that the correct networking software is installed on the system and that the network is accessible.
On NetWare, the error output of tmloadcf could not be redirected to the standard output.
Ensure that there are enough file descriptors available. Try re-running the command, or contact your BEA TUXEDO System Technical Support.
On NetWare, the error output of tmunloadcf could not be redirected to the standard output.
Ensure that there are enough file descriptors available. Try re-running the command, or contact your BEA TUXEDO System Technical Support.
The buildserver command was unable to execute the system compiler. The command that buildserver attempted to execute is given as part of the error message.
Verify that the compiler has been installed on the machine, that it is executable, and that the directory containing the compiler is included in the PATH environment variable. If the name of the compiler is other than the standard cc, set and export the CC shell variable to the proper name of the compiler. Otherwise, verify that the CC shell variable is not set to some extraneous value.
buildserver(1)
An attempt dynamically to allocate memory from the operating system using malloc failed while executing buildserver.
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
An attempt was made to boot a System 5 version of TUXEDO System/T with a System 6 version of TUXEDO System/T with the TUXINTEROP environment variable set to "N". This is not allowed. The system running the older release is printed.
Shut down the application and unset the TUXINTEROP environment variable before re-booting, or upgrade the system in question. Contact your BEA TUXEDO System Technical Support.
An attempt was made to boot a System 5 version of TUXEDO System/T with a System 6 version of TUXEDO System/T with the TUXINTEROP environment variable set to "N". This is not allowed. The system running the older release is printed.
Shut down the application and unset the TUXINTEROP environment variable before re-booting, or upgrade the system in question. Contact your BEA TUXEDO System Technical Support.
An /AdminAPI call accessing the T_BRIDGE class of the TM_MIB(5) with a specified value for the TA_SUSPTIME attribute was disallowed because it accompanied a TA_STATE change to a TA_STATE value other than SUSPENDED.
Omit the TA_SUSPTIME value from the request if you are changing TA_STATE to either ACTIVE or INACTIVE. Otherwise, change the TA_STATE value on the original request to SUSPENDED.
MIB (5), TM_MIB (5)
An /AdminAPI call accessing the T_BRIDGE class of the TM_MIB(5) with a specified value for the TA_SUSPTIME attribute was disallowed because it referenced an occurrence not already in the SUSPENDED state.
Omit the TA_SUSPTIME value from the request or suspend the connection before making the request.
MIB (5), TM_MIB (5)
The buildserver command was run without specifying the -s command line option to indicate service entry points and or services to be advertised for the server. Without at least specifying the service entry points (C functions or COBOL programs), the server will not be able to advertise any services at boot-time or run-time.
Re-run the command specifying services with the -s option.
buildserver (1)
In release 6.1 and earlier, the -L option specified the log file for the tlisten process. In later releases, all logging goes to the userlog and this option is ignored.
No action required.
tlisten(1)
Normally, the tlisten process starts as a background program automatically. The program could not be restarted in the background and will not run.
Check for other messages in the event log. Determine if there is an OS resource that is exhausted and re-try the command when it is resolved.
tlisten(1)
In release 6.1 and earlier, the -L option specified the log file for the tlisten process. In later releases, all logging goes to the userlog and this option is ignored.
No action required.
tlisten(1)
The tlisten process will log the fact that it was able to accept a new connection, after successfully establishing a listening endpoint and opening an accept endpoint on the network. The listening endpoint connection descriptor, fd, and sequence number, number, are placed in the event log.
No action required.
tlisten (1)
A SIGTERM signal was sent to a server in response to a "tmshutdown -w" command or a TMIB request to set the server state to "DEAd".
No action required.
tmshutdown (1), TM_MIB(5)
A SIGKILL signal was sent to a server in response to a "tmshutdown -w" command or a TMIB request to set the server state to "DEAd".
No action required.
tmshutdown (1), TM_MIB(5)
While trying to propagate the TUXCONFIG to a non-master machine, a failure occurred in contacting the tlisten program.
Check for other messages in either the local or remote event log.
tlisten(1), TM_MIB(5)
While trying to propagate the TUXCONFIG to a non-master machine, a failure occurred in contacting the tlisten program.
Check for other messages in either the local or remote event log.
tlisten(1), TM_MIB(5)
The administrative client sbbl could not join the application
There may be too many people attempting to perform MIB operations at the same time. Only 9 sbbl servers may be run at a time, so that if there are more than 9 MIB operations which occur simultaneously, this message may appear. Limit the number of concurrent MIB operations.
The system ran out of memory in the sbbl process
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.
The sbbl process has attempted to open its input file and failed
If the host operating system has a limit on the number of open files, or the number of open files per user or the number of open files per process, then you may need to increase that limit. If it seems that there should be enough file descriptors for this operation, contact your TUXEDO System Technical Support.
The sbbl process has attempted to read its input file and failed
Contact your BEA TUXEDO System Technical Support.
While attempting to boot, the MIB has attempted to open a temporary output file and failed.
If the host operating system has a limit on the number of open files, or the number of open files per user or the number of open files per process, then you may need to increase that limit. The file system /tmp may be full. The directory where temporary files are placed may be full. If it seems that there should be enough file descriptors and disk space for this operation, contact your BEA TUXEDO System Technical Support.
During a boot sequence, the MIB has attempted to write to its output file and failed.
The file system /tmp may be full. The directory where temporary files are placed may be full. If it seems that there should be enough disk space for this operation, contact your BEA TUXEDO System Technical Support.
While attempting to shutdown, the MIB has attempted to open a temporary output file and failed.
If the host operating system has a limit on the number of open files, or the number of open files per user or the number of open files per process, then you may need to increase that limit. The file system /tmp may be full. The directory where temporary files are placed may be full. If it seems that there should be enough file descriptors and disk space for this operation, contact your BEA TUXEDO System Technical Support.
During a shutdown sequence, the MIB has attempted to write to its output file and failed
The file system /tmp may be full. The directory where temporary files are placed may be full. If it seems that there should be enough disk space for this operation, contact your BEA TUXEDO System Technical Support.
Memory allocation failed while retrieving MIB attributes.
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.
While retrieving MIB attribute information, a failure occurred, so the tmconfig operation will fail.
Check the log for related messages.
While retrieving MIB attribute information, a failure occurred, so the tmconfig operation will fail.
Check the log for related messages.
While the sbbl process was attempting to shut down a process, the system ran out of memory.
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.
While the sbbl process was attempting to shut down a process, the system ran out of memory.
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.
A failure occurred while the MIB was attempting to retrieve information about an object which was going to be deactivated.
Contact your BEA TUXEDO System Technical Support.
While the sbbl process was attempting to start a process, the system ran out of memory.
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.
A failure occurred while the MIB was attempting to retrieve information about an object which was going to be activated.
Contact your BEA TUXEDO System Technical Support.
While attempting to generate an encryption packet for the TAGENT on the given site, a memory allocation error occurred.
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.
A process attempted to contact the tlisten. However, the MINENCRYPTBITS field in the *NETWORK section for this process was set to a value greater than 0. No encryption package is installed.
Buy and install the Link Level Encryption package or reconfigure the system such that MINENCRYPTBITS is 0.
A process attempted to contact the tlisten. However, the MINENCRYPTBITS field in the *NETWORK section for this process was set to a value greater than 40. Only the 40-bit Link Level Encryption package is installed.
Buy and install the 128-bt Link Level Encryption package or reconfigure the system such that MINENCRYPTBITS is less than or equal to 40.
The link level encryption packet which contained the Diffie-Hellman key exchange information was corrupted. The network may be compromised.
Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
The process attempting to connect to the TAGENT could not successfully negotiate an encryption strength.
There are many ways to fix this problem. One is to change the encryption parameters in the *NETWORK section for the connecting machine to be compatible with the options with which the remote tlisten was started. The second is to kill the remote tlisten, and restart it using different parameters for the -z and -Z options. If you do not specify any -z or -Z options to the tlisten process, then by default it will speak any encryption protocol allowed in the currently installed package. To find out which package is installed on any site, run the command tmadmin -v. If your application is connecting to an older site, then you must configure the system such that it can speak 0 bits of encryption to the older site.
The link level encryption packet which contained the Diffie-Hellman key exchange information was corrupted. The network may be compromised.
Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
The process attempting to connect to the TAGENT could not successfully negotiate an encryption strength.
There are many ways to fix this problem. One is to change the encryption parameters in the *NETWORK section for the connecting machine to be compatible with the options with which the remote tlisten was started. The second is to kill the remote tlisten, and restart it using different parameters for the -z and -Z options. If you do not specify any -z or -Z options to the tlisten process, then by default it will speak any encryption protocol allowed in the currently installed package. To find out which package is installed on any site, run the command tmadmin -v. If your application is connecting to an older site, then you must configure the system such that it can speak 0 bits of encryption to the older site.
The MINENCRYPTBITS field in the NETWORK section of the UBBCONFIG file must be set to 0, 40 or 128.
MINENCRYPTBITS is the minimum allowable level of encryption which may be used by the BRIDGE on this network address. Change the MINENCRYPTBITS field in the UBBCONFIG file to 0, 40 or 128. The encryption level which gets negotiated at run-time can be determined from the TA_CURENCRYPTBITS field in the BRIDGE class.
The MAXENCRYPTBITS field in the NETWORK section of the UBBCONFIG file must be set to 0, 40 or 128.
MAXENCRYPTBITS is the prefered level of encryption which may be used by the BRIDGE on this network address. Change the MAXENCRYPTBITS field in the UBBCONFIG file to 0, 40 or 128. The encryption level which gets negotiated at run-time can be determined from the TA_CURENCRYPTBITS field in the BRIDGE class.
The system ran out of memory in the tlisten process while attempting to allocate an encryption handle.
Check the memory on the system where the command was run. If it seems that there should be enough memory for this operation, contact your TUXEDO System/T Technical Support.
The -z option of the tlisten must be set to 0, 40 or 128.
The -z option is the minimum allowable level of encryption which may be used by this tlisten. Change the -z option to 0, 40 or 128.
The -Z option of the tlisten must be set to 0, 40 or 128.
The -Z option is the prefered level of encryption which may be used by this tlisten. Change the -Z option to 0, 40 or 128.
The -z option was larger than zero. However, the link level encryption package was not installed.
Buy the link level encryption package. Set the -z option to 0. If you believe that you have installed the link level encryption package, contact your TUXEDO System/T Technical Support.
The -z option was larger than forty. The 40-bit package is installed.
Buy the 128-bit link level encryption package. Set the -z option to 0 or 40. If you believe that you have installed the 128-bit link level encryption package, contact your BEA TUXEDO System Technical Support.
A site older than the Titan release attempted to contact a tlisten whose -z option was set greater than 0.
When older sites are part of a TUXEDO System/T configuration, the -z option of the tlisten may have to be zero in order for proper communication between the older site and the newer site. By restarting the tlisten process with a -z option of zero (or no -z option, since by default the minimum encryption parameter is zero), then older sites may successfully connect to this tlisten process.
The link level encryption packet which contained the Diffie-Hellman key exchange information was corrupted. The network may be compromised.
Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
An error occurred in the network when attempting to send an encryption packet.
Check the network on the system where the tlisten is running. If it seems that the network is working properly, contact your BEA TUXEDO System Technical Support.
The process attempting to connect to the tlisten could not successfully negotiate an encryption strength.
There are many ways to fix this problem. One is to change the encryption parameters in the *NETWORK section for the connecting machine to be compatible with the options with which the remote tlisten was started. The second is to kill the remote tlisten, and restart it using different parameters for the -z and -Z options. If you do not specify any -z or -Z options to the tlisten process, then by default it will speak any encryption protocol allowed in the currently installed package. To find out which package is installed on any site, run the command tmadmin -v. If your application is connecting to an older site, then you must configure the system such that it can speak 0 bits of encryption to the older site.
The link level encryption packet which contained the Diffie-Hellman key exchange information was corrupted. The network may be compromised.
Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
The BRIDGE or BSBRIDGE could not boot because it was not configured correctly. The MINENCRYPTBITS field in the *NETWORK section was set to a value greater than 0. No encryption package is installed.
Buy and install the Link Level Encryption package or reconfigure the system such that MINENCRYPTBITS is 0.
The BRIDGE or BSBRIDGE could not boot because it was not configured correctly. The MINENCRYPTBITS field in the *NETWORK section was set to a value greater than 40. Only the 40-bit Link Level Encryption package is installed.
Buy and install the 128-bt Link Level Encryption package or reconfigure the system such that MINENCRYPTBITS is less than or equal to 40.
The system ran out of memory
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.
While generating the first link level encryption negotation package for BRIDGE communication, an error occurred.
Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
While sending the first link level encryption negotation package for BRIDGE communication, an error occurred.
Check the network on the machine with the affected BRIDGE or BSBRIDGE.
The system ran out of memory in the BRIDGE or BSBRIDGE
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.
While generating the second link level encryption negotation package for BRIDGE communication, an error occurred.
Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
While sending the second link level encryption negotation package for BRIDGE communication, an error occurred.
Check the network on the machine with the affected BRIDGE or BSBRIDGE.
The BRIDGE or BSBRIDGE attempting to connect to the BRIDGE or BSBRIDGE on the given remote site could not successfully negotiate an encryption strength.
Change the encryption parameters in the *NETWORK section for the two machines connecting to each other to be compatible.
A system error occurred during link level encryption negotation.
Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
A system error occurred during link level encryption negotation.
Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
A system error occurred during link level encryption negotation.
Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
While the BRIDGE or BSBRIDGE is negotiating the link level encryption parameters, messages to the remote BRIDGE are saved. An error occurred while sending these saved messages to the remote BRIDGE after the negotiation was complete.
Check the network on the machine with the affected BRIDGE or BSBRIDGE.
During the tmboot process, the *SERVERS section of the configuration file could not be read.
Verify that the environment variable TUXCONFIG is set correctly and exported. Make sure the TUXCONFIG file is not corrupted (try a tmunloadcf ). Verify that the TUXCONFIG file was propagated to all machines in the configuration.
tmboot (1), tmunloadcf (1)
During the tmshutdown process, the *SERVERS section of the configuration file could not be read.
Verify that the environment variable TUXCONFIG is set correctly and exported, or that TUXCONFIG is not corrupted (try a tmunloadcf )
A remote machine has been marked as partitioned, but has not been cleaned from the bulletin board using the tmadmin pclean command (or the equivalent MIB operation).
Firt pclean the remote machine by using tmadmin (or the GUI, or the MIB). Once the pclean has completed successfully, try to boot the remote BBL again. If the remote boot fails again, contact your BEA TUXEDO System Technical Support.
The tlisten could not access the authentication files.
Make sure that the administrator has read priveledges on the $TUXDIR/udataobj/tlisten.pw file or the $APPDIR/.adm/tlisten.pw file. Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
The remote tlisten could not access the authentication files.
Make sure that the administrator has read priveledges on the $TUXDIR/udataobj/tlisten.pw file or the $APPDIR/.adm/tlisten.pw file on the remote site. Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
While authenticating with the tlisten process, an error occurred while reading the password file
The password file is $TUXDIR/udataobj/tlisten.pw or $APPDIR/.adm/tlisten.pw. Make sure that this file is not corrupted or missing. If everything in the file appears normal, contact your BEA TUXEDO System Technical Support.
The tlisten process may attempt to change directories to $APPDIR during authentication. If the process cannot change directories, this error may occur.
Make sure that the APPDIR of the current application is not corrupted or missing. If everything in the directory appears normal, contact your TUXEDO System/T Technical Support.
While authenticating with the tlisten process, an error occurred while reading the password file.
The password file is $TUXDIR/udataobj/tlisten.pw or $APPDIR/.adm/tlisten.pw. Make sure that this file is not corrupted or missing. If everything in the file appears normal, contact your BEA TUXEDO System Technical Support.
While authenticating with the tlisten process, an error occurred while reading the password file.
The password file is $TUXDIR/udataobj/tlisten.pw or $APPDIR/.adm/tlisten.pw. Make sure that this file is not corrupted or missing. If everything in the file appears normal, contact your BEA TUXEDO System Technical Support.
tlisten authentication has been turned off. No site will be authenticated. Be warned that the tlisten may be the site of a security breach.
The password file is $TUXDIR/udataobj/tlisten.pw or $APPDIR/.adm/tlisten.pw. The password file is a plain-text file where each line (up to 20) contains a password. The password file on the remote site must contain at least one password which is the same as a password on the local site. If you create this file, and restart the tlisten or other process which may have to speak to the tlisten, then this warning will not be displayed. If this warning is not displayed, then the network session with the remote site will be authenticated.
In order to properly authenticate the tlisten session, an encryption package must be installed.
Contact your BEA TUXEDO System Technical Support.
The system found the tlisten authentication password file, but could not open it.
If the host operating system has a limit on the number of open files, or the number of open files per user or the number of open files per process, then you may need to increase that limit. If it seems that there should be enough file descriptors for this operation, contact your TUXEDO System Technical Support.
The tlisten authentication file will only accept the first twenty passwords. All subsequent passwords will be ignored.
Limit the number of passwords in the tlisten password authentication file to twenty.
Passwords found in the tlisten authentication file can only be the specified number of characters long. All characters after the maximum number of characters will be ignored.
Limit the number of characters for each password in the tlisten password authentication file to the specified amount.
There must be at least one password in the password authentication file in order for tlisten authentication to work properly.
The password file is $TUXDIR/udataobj/tlisten.pw or $APPDIR/.adm/tlisten.pw. Add a password to the password file. One suggestion for a password is abracadabra.
The remote site did not have a matching password in its password file.
Make sure that there is a password on the local site which matches one of the passwords on the remote site. Monitor your network for malicious use. Contact your BEA TUXEDO System Technical Support.
The network returned an error during authentication with the tlisten.
Check the network on the system where the command was run. If the network is OK, then contact your BEA TUXEDO System Technical Support.
Authentication with the remote tlisten failed.
Make sure that there is a password on the local site which matches one of the passwords on the remote site. Monitor your network for malicious use. Contact your BEA TUXEDO System Technical Support.
Authentication with the remote tlisten failed.
Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
Authentication with the remote tlisten failed.
Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
While the BRIDGE or BSBRIDGE is negotiating the link level encryption parameters, messages to the remote BRIDGE are saved. An error occurred while sending these saved messages to the remote BRIDGE after the negotiation was complete.
Check the network on the machine with the affected BRIDGE or BSBRIDGE.
An error occurred while converting a non-ASCII tlisten password file into ASCII for authentication purposes.
Contact your BEA TUXEDO System Technical Support.
A process speaking to a tlisten sent an invalid link level encryption negotiation opcode.
The process on the remote site may be attempting to circumvent link level encryption. Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
The tlisten on the remote site sent an invalid link level encryption negotiation opcode.
The tlisten on the remote site may be attempting to circumvent link level encryption. Monitor your network for malicious use. Contact your TUXEDO System Technical Support.
The process attempting to contact the tlisten could not generate the first encryption packet.
Contact your BEA TUXEDO System Technical Support.
The NADDR parameter in the *NETWORK section of the UBBCONFIG file was not in the correct format.
Any address in the NADDR field 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. Change the NADDR field to comply with the known formats. If you believe that your address is in the proper format, contact your TUXEDO System Technical Support.
The NLSADDR parameter in the *NETWORK section of the UBBCONFIG file was not in the correct format.
Any address in the NLSADDR field 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. Change the NLSADDR field to comply with the known formats. If you believe that your address is in the proper format, contact your TUXEDO System Technical Support.
A TUXEDO System release greater than or equal to Release 6.3 attempted to send an internet address to an older release.
Releases of the TUXEDO System prior to the Release 6.3 release do not understand the internet address naming schemes. When interoperating with an older release, the older method of specifying addresses must be used. Replace internet addresses with the older "0x" style of address.
While attempting to get the NT service name, an error occurred while opening the service manager.
Contact your BEA TUXEDO System Technical Support.
While attempting to get the NT service name the task ran out of memory.
Check the memory on the system where the command was run. If it seems that there should be enough memory for this operation, contact your TUXEDO System/T Technical Support.
While attempting to set the NT service status an error occurred.
Contact your BEA TUXEDO System Technical Support.
While attempting to register the NT service an error occurred.
Contact your BEA TUXEDO System Technical Support.
While attempting to set the NT service status an error occurred.
Contact your BEA TUXEDO System Technical Support.
While attempting to access the NT registry an error occurred.
Contact your BEA TUXEDO System Technical Support.
While attempting to access the NT registry an error occurred.
Contact your BEA TUXEDO System Technical Support.
While attempting to start the specified NT service an error occurred.
Contact your BEA TUXEDO System Technical Support.
The tlisten process has started properly
None
A memory allocation failure occurred in tmconfig
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.
While tmconfig was processing a request, tpcall failed.
Check the error code which tpcall returned. Check the userlog to see if any more information is available. Contact your BEA TUXEDO System Technical Support.
While the tlisten was allocating memory for the network address it ran out of memory.
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.
While the tlisten was allocating memory for the network address it ran out of memory.
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.
An illegal tlisten network address was specified.
Specify the tlisten network address with the -l option.
The AS400 could not execute the given command.
Check the command syntax to be sure it is proper. If it is proper and the executable referenced in the command line is currently executable, contact your BEA TUXEDO System Technical Support.
The AS400 could not execute the given command.
Check the command syntax to be sure it is proper. If it is proper and the executable referenced in the command line is currently executable, contact your BEA TUXEDO System Technical Support.
Memory allocation failed while building a server.
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.
The AS400 ran out of memory in the tmloadcf process.
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.
The AS400 ran out of memory in the tmloadcf process.
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.
tmconfig could not find the TUXCONFIG file or could not read 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/T. Shut down the system, remove the file, and recreate it with tmloadcf. If the trouble persists, contact your BEA TUXEDO System Technical Support.
The TUXCONFIG environment variable must be set for tmconfig to work properly
Set the TUXCONFIG environment variable to point to the TUXCONFIG file of the application which you would like to configure.
The TUXCONFIG environment variable must be set for ud or ud32 to work properly
Set the TUXCONFIG environment variable to point to the TUXCONFIG file of the application which you would like to use ud or ud32 on.
ud or ud32 could not find the TUXCONFIG file or could not read 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/T. Shut down the system, remove the file, and recreate it with tmloadcf. If the trouble persists, contact your BEA TUXEDO System Technical Support.
The BRIDGE process could not establish its listening address for incoming network connections.
Check the NADDR and BRIDGE parameters for this machine in the *NETWORK section of the configuration file.
The BRIDGE process could not establish a connection to the remote machine and address. There may be networking problems, or the remote machine may have crashed.
Check that the remote machine is up.
Check network connectivity between the machines.
Check that the BRIDGE is running on the remote machine at the given address.
The BRIDGE process will automatically reestablish a connection between the machines on demand, when possible. To prevent thrashing, the link will be suspended for five minutes if an automatic reconnect attempt fails. No further automatic reconnection attempts are made during this interval. If desired, use tmadmin(1)'s reconnect command to initiate a reconnection attempt manually. Manual attempts are allowed during the five-minute suspension interval.
The BRIDGE process could not reconnect to machine during recovery from a networking problem.
Check that machine is up.
Check network connectivity between the machines.
Check that the TUXEDO System is running on machine.
The BRIDGE processes will automatically reestablish a connection between the machines on demand, when possible. To prevent thrashing, the link will be suspended for five minutes if an automatic reconnect attempt fails. No further automatic reconnection attempts are made during this interval.
If desired, use tmadmin (1)'s reconnect command to initiate a reconnection attempt manually. Manual attempts are allowed during the five-minute suspension interval.
Messages 1375 and 1374 and tmadmin (1)'s reconnect command
The tlisten could not establish an endpoint for listening at the given address.
Ensure that the listening endpoint is free for use by the tlisten process. If it is not, choose a different endpoint. On some operating systems, there is a long delay while the listening port is cleared. Wait 5 minutes, and try the command again.
An error occurred while tmconfig32 was setting the FLDTBLDIR32 variable.
Contact your BEA TUXEDO System Technical Support.
An error occurred while tmconfig32 was setting the FIELDTBLS32 variable.
Contact your BEA TUXEDO System Technical Support.
command (tpaddusr, tpmodusr, or tpdelusr) was run with a filename of /etc/passwd. These commands may delete important information from /etc/passwd and cannot be used to modify it directly.
Modify the /etc/passwd file directly using a text editor or use a different user file.
While checking the status of the sbbl process, the DBBL or BBL ran out of memory.
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.
The sbbl was not able to finish a MIB request. The DBBL or BBL sent a message to that effect to the requestor.
Check the log for related messages.
While checking the status of the sbbl process, the DBBL or BBL ran out of memory.
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.
This message indicates that a new machine has been booted and records the internal release number. This information may be useful to TUXEDO System/T support, if necessary.
No action necessary.
This message is printed by the DBBL during the first sanity check after midnight for each booted machined. This information may be useful to TUXEDO System/T support, if necessary.
No action necessary.
While building a server, one of the specified service names is longer than the maximum allowed. The name will be truncated.
No action is required. However, it is recommended that the name be shortened to the maximum allowed, as indicated by the message.
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.
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 error occurred while retrieving the current license attributes.
Contact your BEA TUXEDO System Technical Support.
You do not have a license to use /Events.
Purchase a license for /Events. If you believe that you own and have installed the license for /Events, contact your BEA TUXEDO System Technical Support.
An error occurred while retrieving the current license attributes.
Contact your BEA TUXEDO System Technical Support.
You do not have a license to use /Events.
Purchase a license for /Events. If you believe that you own and have installed the license for /Events, contact your BEA TUXEDO System Technical Support.
An error occurred while retrieving the current license attributes.
Contact your BEA TUXEDO System Technical Support.
You do not have a license to use Transactions.
Purchase a license for Transactions. If you believe that you own and have installed the license for Transactions, contact your BEA TUXEDO System Technical Support.
Message allocation failed for getting a message buffer by sbbl when sending message to DBBL to update sbbl sanity table.
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
sbbl can not find DBBL entry in the Bulletin Board. The Bulletin Board may be corrupted.
Contact your BEA TUXEDO System Technical Support.
sbbl can not send message to DBBL to update sbbl sanity table.
Contact your BEA TUXEDO System Technical Support.
DBBL took actions to send an error message to the blocking MIB operation requestor when DBBL found an expired entry in the sbbl sanity table. The possible cause could be sbbl can not successfully register with Bulletin Board.
Reduce the number of blocking MIB operation at the same time. If the problem still occurs then contact your BEA TUXEDO System Technical Support.
sbbl took actions to send an error message to the blocking MIB operation requestor when sbbl can not successfully register with Bulletin Board as a regular client process.
Reduce the number of blocking MIBS operation at the same time. If the problem still occurs then contact your BEA TUXEDO System Technical Support.
Memory allocation failed for getting a TPINIT buffer by sbbl when registering with Bulletin Board as a regular client.
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
The value used for DBBLWAIT (* 2) is greater than the value in BLOCKTIME.
Check the values used for both variables and adjust accordingly.
The value used for DBBLWAIT (* 2) is greater than the value in BLOCKTIME.
Check the values used for both variables and adjust accordingly.
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.
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.
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.
An error occured while converting address to an internal binary representation.
Contact your BEA TUXEDO System Technical Support.
ud or ud32 could not resize the TPINIT buffer
ud or ud32 may attempt to resize the TPINIT buffer when there is more user authentication data than expected. reason-code may provide insight into the cause of this failure. Make sure enough memory exists on the system running ud or ud32. If it appears that there should be enough memory to ud or ud32, and this error happens consistently, then contact the BEA TUXEDO System Technical Support.
While booting a new node, the licensed features did not match those features licensed on the master node. This could potentially cause inconsistent results if the master node is migrated to this site or if certain capabilities are accessed from that site.
Ensure that the license file in $TUXDIR/udataobj on each machine in the application has the same features licensed to insure consistent behavior.
A permissions violation has occurred while attempting to process an /AdminAPI SET request on the indicated class object. The attribute TA_BADFLD is set on the reply to indicate the field that is in violation of permissions.
The administrator can tune permissions for any attribute user combination to the maximum supported by the system. However, write access is not supported on all attributes in all class object states. Therefore, the update may need to be delayed until the class object is in a different state.
Creation of a temporary file in tmconfig using crtsrcpf on the AS/400 failed.
Ensure that there is sufficient space in /qsys.lib/qtemp.lib and re-run the operation.
Creation of a temporary file in tmconfig using crtsrcpf on the AS/400 failed.
Ensure that there is sufficient space in /qsys.lib/qtemp.lib and re-run the operation.
buildclient(1) was running without having a valid TUXEDO System SDK license (e.g., only and RTK license was installed).
Buy a TUXEDO System SDK license.
buildserver(1) was running without having a valid TUXEDO System SDK license (e.g., only and RTK license was installed).
Buy a TUXEDO System SDK license.
An attempt to dynamically allocate memory from the operating system using malloc() failed while parsing the UBBCONFIG file.
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
An attempt to dynamically allocate memory from the operating system using malloc() failed while parsing the UBBCONFIG file.
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
While parsing the UBBCONFIG file, a hex escape sequence was found with a value larger than will fit in a single character (i.e., greater than 0xff).
Correct the value and re-run tmloadcf(1).
While parsing the UBBCONFIG file, a backslash escape preceding a character that is not a valid escape sequence (t, n, f, b, r, 0, backslash, n, x, or X).
Correct the value and re-run tmloadcf(1).
While parsing the UBBCONFIG file, an octal escape sequence was found with a value larger than will fit in a single character (i.e., greater than 0xff).
Correct the value and re-run tmloadcf(1).
While parsing the UBBCONFIG file, a backslash escape preceding a character that is not a valid escape sequence (t, n, f, b, r, 0, backslash, n, x, or X).
Correct the value and re-run tmloadcf(1).
While running tmboot or tmshutdown on the AS/400, the program could not re-direct the standard error output into a file.
Re-run the operation. Ensure that there is sufficient file space.
The event server couldn't open file file for reading the subscription database.
The event server reads a new copy of the subscription database from the temporary file file. This message indicates that the server couldn't open the temporary file for reading. Check the file system parameters and take corrective action.
An error occurred attempting to open the input file specified as -ifile on the command line for UD or UD32.
Make sure the input file file exists and is readable.
An error occurred attempting to open the output file file for write as specified by -ofile on the command line for UD or UD32.
Make sure file system limit has not been exceeded and user has write permissions for the directory in which the output file is to be created.
On some platforms the a TCP port may be help for up to four minutes by the operating system after use. The BRIDGE process will try to establish a port for ninty seconds before giving up completely. This message will print out every fifteen seconds with the amount of time which the BRIDGE process will wait for a hung port.
Ensure that the TCP port number being used by the BRIDGE is not in use by some other process. On some operating systems, the netstat command can be used to determine the state of TCP ports.
The BRIDGE could not allocate memory for a network descriptor.
The BRIDGE ran out of memory when attempting to contact address. Make sure enough memory exists on the system running the BRIDGE. If it appears that there should be enough memory to run the BRIDGE, and this error happens consistently, then contact the BEA TUXEDO System Technical Support.
An operating system error occured while attempting to change the state of the network descriptor from blocking to non-blocking.
If this error happens consistently, then contact the TUXEDO System Technical Support.
An operating system error occured while attempting to change the state of the network descriptor from non-blocking to blocking.
If this error happens consistently, then contact the TUXEDO System Technical Support.
Link level encryption was used on a network link which has gone bad. Since the message to be sent was encrypted, it cannot be recovered and sent to an alternate address.
None.
While compiling the UBBCONFIG file an error occured. NETGRPNO numbers must be between 0 and highval.
Change the NETGRPNO value to be within the required range.
An attempt dynamically to allocate memory from the operating system using calloc () failed while trying to allocate space for an network descriptor in the BRIDGE.
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.
The administrator attempted to change the state of the BRIDGE from ACTIVE to PENDING or from PENDING to ACTIVE.
This MIB state change should not be attempted.
An operating system error occured while attempting to poll the network descriptors.
If this error happens consistently, then contact the TUXEDO System Technical Support.
The bridge received a packet with an unknown release number value. The network may be having difficulty. If link level encryption is in use, this error may be an indication that an attack is in progress.
If this error happens consistently, then contact the TUXEDO System Technical Support.
The BRIDGE has messages which are used to syncronize communications. One of these messages has been recieved from another BRIDGE, but the format is unknown.
If this error happens consistently, then contact the TUXEDO System Technical Support.
While compiling the UBBCONFIG file an error occured. MAXPENDINGBYTES must be greater than or equal to 100000.
Change the MAXPENDINGBYTES value to be greater than or equal to 100000.
While compiling the UBBCONFIG file an error occured. There may only be one *NETGROUPS section in the UBBCONFIG file.
Remove duplicate NETGROUPS sections from the UBBCONFIG file.
While compiling the UBBCONFIG file an error occured. A network group name must be less than or equal to value characters.
Shorten the name of the network group in the *NETGROUPS section.
While compiling the UBBCONFIG file an error occured. The network group name name may not contain certain characters.
Remove the undesirable characters from name.
While compiling the UBBCONFIG file an error occured. A duplicate network group entry was found.
Network group names must be unique. Choose another name for this network group.
An attempt dynamically to allocate memory from the operating system using malloc () failed during tmloadcf while trying to allocate space for the network group table.
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 realloc () failed during tmloadcf while trying to allocate space for the network group table.
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 during tmloadcf while trying to allocate space for the network group name.
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 compiling the UBBCONFIG file an error occured. The maximum number of network groups allowed in a configuration is controlled by the *RESOURCES parameter MAXNETGROUPS. The number of netgroups found in the UBBCONFIG file is greater than the maximum number of netgroups.
Either remove network groups or increase the value of MAXNETGROUPS.
While compiling the UBBCONFIG file an error occured. NETGRPNO is a required parameter for each entry in the *NETGROUPS section. entry did not supply the required parameter.
Supply a network group number for the entry network group. Network group numbers must be unique, and should remain consitent for the life of the network group. The network group number is used to coordinate failover and failback of the network.
While compiling the UBBCONFIG file an error occured. NETGRPNO is a required parameter for each entry in the *NETGROUPS section, and must be unique. entry did not supply a unique NETGRPNO parameter.
Supply a network group number for the entry network group. Network group numbers must be unique, and should remain consitent for the life of the network group. value is not unique. The network group number is used to coordinate failover and failback of the network.
While compiling the UBBCONFIG file an error occured. NETGRPNO is a required parameter for each entry in the *NETGROUPS section, and must be unique. There is always at least one network group named DEFAULTNET which has a NETGRPNO of zero. Hence, network group entry may not have a NETGRPNO of zero.
Supply a network group number for the entry network group. Network group numbers must be unique, and should remain consitent for the life of the network group. value is not unique, since the network group DEFAULTNET has a NETGRPNO of zero. The network group number is used to coordinate failover and failback of the network.
While compiling the UBBCONFIG file an error occured. The MAXNETGROUPS parameter must be between lowval and highval.
Change the MAXNETGROUPS value to be within the required range.
While compiling the UBBCONFIG file an error occured. The *NETGROUPS section must appear before the *RESOURCES section.
Place the *NETGROUPS section after the *RESOURCES section.
While compiling the UBBCONFIG file an error occured. The network priority of a network group must be greater than zero and less than or equal to value.
Change the NETPRIO parameter to be within the required range.
While compiling the UBBCONFIG file an error occured. The *NETGROUPS section must appear before the *NETWORK section.
Place the *NETWORK section after the *NETGROUPS section.
An attempt dynamically to allocate memory from the operating system using calloc () failed during tmloadcf while trying to allocate space for the network map table.
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.
The BRIDGE could not find the machine section of the TUXCONFIG file.
The TUXCONFIG file may be corrupt. If this machine is the master node, try removing the TUXCONFIG file and regenerating it from the UBBCONFIG using tmloadcf. If this machine is a remote node, make sure that all IPC resources have been removed from the machine. Then remove the TUXCONFIG file, and attempt to tmboot the machine from the MASTER machine. If this error happens consistently, then contact the TUXEDO System Technical Support.
The BRIDGE could not find the LMID name in the TUXCONFIG file. The BRIDGE is searching for its own entry in the TUXCONFIG file.
The TUXCONFIG file may be corrupt. If this machine is the master node, try removing the TUXCONFIG file and regenerating it from the UBBCONFIG using tmloadcf. If this machine is a remote node, make sure that all IPC resources have been removed from the machine. Then remove the TUXCONFIG file, and attempt to tmboot the machine from the MASTER machine. If this error happens consistently, then contact the TUXEDO System Technical Support.
An attempt to dynamically allocate memory from the operating system using malloc () failed while trying to allocate space for communication with the tlisten.
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. There may be a security attack in progress.
An attempt was made to use link level encryption of min bits on a network link. However, the link level encryption package has not been installed on this machine.
Install the link level encryption package on this machine, or change the MINENCRYPTBITS value of min for this network entry to zero.
While compiling the UBBCONFIG file an error occured. In the *NETWORK section, each entry must match a corresponding entry in the *MACHINES section. name does not match any entry in the *MACHINES section.
Either remove the *NETWORK section entry or add a *MACHINE section entry corresponding to the given LMID.
While compiling the UBBCONFIG file an error occured. The NETGROUPS parameter of a *NETWORK section entry must match a netgroup previously defined in the *NETGROUPS section. name does not match any entry in the *NETGROUPS section.
Either remove the *NETWORK section entry or add a *NETGROUPS section entry corresponding to the given NETGROUP parameter.
An attempt was made to use link level encryption of min bits on a network link. However, the installed link level encryption package is fourty bit.
Install the one hundred twenty eight link level encryption package on this machine, or change the MINENCRYPTBITS value of min for this network entry to zero or fourty.
The BRIDGE was attempting to discover network parameters pertaining to its own set of netgroups. However, it could not find any network groups for which it is a member.
Ensure that every machine in a network application is a member of a network group. All machines should be members of the DEFAULTNET group, and may also be members of any other network group.
The TA_NETGROUP field may not be set during a SET operation of the T_BRIDGE class.
Remove the TA_NETGROUP field from all SET operations involving the T_BRIDGE class.
While compiling the UBBCONFIG file an error occured. The value of NETGRPNO for the netgroup network group must be zero.
netgroup is a special network group which must have a NETGRPNO value of zero. Change NETGRPNO for this network group to zero.
An attempt dynamically to allocate memory from the operating system using realloc () failed during tmloadcf while trying to allocate space for the network map table.
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 compiling the UBBCONFIG file an error occured. No two entries in the *NETWORK section may have the same LMID and NETGROUP attributes.
Ensure that all entries in the *NETWORK section have a unique combination of LMID and NETGROUP values. In particular, more than one lmid entry has a NETGROUP parameter of netgroup.
While compiling the UBBCONFIG file an error occured. A network group name must be less than or equal to value characters.
Shorten the name of the NETGROUP field in the *NETWORK section.
An attempt dynamically to allocate memory from the operating system using malloc () failed while trying to allocate space for an internal ciruit table in the BRIDGE.
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. The use of MAXPENDINGBYTES in the machines section may alleviate the BRIDGE memory allocation problem.
While attempting to connect to the LMID lmid, the BRIDGE process could not find an address to connect to in the TUXCONFIG file.
Ensure that an entry exists for lmid in the UBBCONFIG *NETWORK section. If an entry exists, contact your BEA TUXEDO System Technical Support.
While attempting to connect to the LMID lmid, the BRIDGE process could not find an address to connect to in the TUXCONFIG file.
Ensure that an entry exists for lmid in the UBBCONFIG *NETWORK section. If an entry exists, contact your BEA TUXEDO System Technical Support.
An operating system error occured while attempting to initialize network information. The tlisten will not boot.
Ensure the viability of the network. If the network appears to be viable, 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 internal ciruit table in the BRIDGE.
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. The use of MAXPENDINGBYTES in the machines section may alleviate the BRIDGE memory allocation problem.
An attempt dynamically to allocate memory from the operating system using malloc () failed while the BRIDGE was connecting to lmid.
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. The use of MAXPENDINGBYTES in the machines section may alleviate the BRIDGE memory allocation problem.
An internal error was captured by the BRIDGE.
Contact your BEA TUXEDO System Technical Support.
An operating system error occured while attempting to initialize network information. The tlisten will not boot.
Ensure the viability of the network. If the network appears to be viable, contact your BEA TUXEDO System Technical Support.
An operating system error occured while attempting to initialize network information. The tlisten will not boot.
Ensure the viability of the network. If the network appears to be viable, contact your BEA TUXEDO System Technical Support.
The tlisten received a packet with an unknown release number value. The network may be having difficulty. If link level encryption is in use, this error may be an indication that an attack is in progress.
If this error happens consistently, then contact the TUXEDO System Technical Support.
A network descriptor could not be allocated for the listening endpoint in the tlisten.
Ensure the network on the system is viable. If this error happens consistently, then contact the BEA TUXEDO System Technical Support.
A process speaking to a tlisten process could not decrypt one of the messages coming from the tlisten. This error may indicate that an attack is in progress.
Ensure the network on the system is viable. If this error happens consistently, then contact the BEA TUXEDO System Technical Support.
A process speaking to a tlisten process could not encrypt a message for the tlisten on lmid. This error may indicate that an attack is in progress.
Ensure the network on the system is viable. If this error happens consistently, then contact the BEA TUXEDO System Technical Support.
tmshutdown was unable to send a SIGTERM to a server of the given id and grp. The value of tperrno may provide further information on the source of the failure.
None.
tmshutdown was unable to send a SIGKILL to a server of the given id and grp. The value of tperrno may provide further information on the source of the failure.
None.
tmshutdown was unable to send a SIGTERM to a server of the given id and grp. The value of tperrno may provide further information on the source of the failure.
None.
tmshutdown was unable to send a SIGKILL to a server of the given id and grp. The value of tperrno may provide further information on the source of the failure.
None.
The tlisten could not get a resource necessary to perform link level encryption.
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.
The NETGRPNO of a the remote lmid machine does not match the value given in the local version of the TUXCONFIG file. This error may indicate that a security attack was in progress.
Ensure the network is viable and that there were no security attacks in progress. It may be necessary to bring the affected machine down, remove its TUXCONFIG file and tmboot the machine.
The BBL has killed a server due to a service time-out. The server is described by its queue, group and srvid.
The administrator may need to configure the service time-out higher in order to accomodate a heavily loaded system.
The given mid has become unpartitioned.
None
The given mid has become unpartitioned.
None
The given mid has become unpartitioned.
None
The BRIDGE process saves messages while an asyncronous connect is outstanding. However, once the connection was established, there was an error sending the messages saved for the remote machine.
Ensure that the network connection is viable. If the network is flaky, it is possible that the connection establishment packet was received, but that subsequent packets were lost by the network. If the network appear to be viable, contact your BEA TUXEDO System Technical Support.
The BRIDGE failed to allocate memory.
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.
Check that machine is up.
Check network connectivity between the machines.
Check that the TUXEDO System is running on machine.
The BRIDGE processes will automatically reestablish a connection between the machines on demand, when possible. To prevent thrashing, the link will be suspended for five minutes if an automatic reconnect attempt fails. No further automatic reconnection attempts are made during this interval.
If desired, use tmadmin (1)'s reconnect command to initiate a reconnection attempt manually. Manual attempts are allowed during the five-minute suspension interval.
While the BRIDGE or BSBRIDGE is negotiating the link level encryption parameters, messages to the remote BRIDGE are saved. An error occurred while sending these saved messages to the remote BRIDGE after the negotiation was complete.
Check the network on the machine with the affected BRIDGE or BSBRIDGE.