CMDTUX Messages 0-99
|
|
|
1
ERROR: End time is before start time
Description
The txrpt utility was run with a start time (-s option) later than the end time (-e option).
Action
Re-run the command with correct start and end options.
See Also
txrpt(1)
10
ERROR: Name table full
Description
Too many service names were supplied with the txrpt utility's -n option, causing an internal table to overflow.
Action
Re-run the command with fewer service names, or contact your BEA TUXEDO system Technical Support.
See Also
txrpt(1)
15
ERROR: txrpt: bad -d arg
Description
The txrpt command was called with an invalid parameter for the -d option.
Action
Retry the command with a corrected -d option.
See Also
txrpt(1)
16
ERROR: txrpt: bad -d option value arg
Description
The txrpt command was called with an invalid parameter for the -d option.
Action
Retry the command with a corrected -d option.
See Also
txrpt(1)
17
WARN: BBL tpsvrinit: bad command line options were specified when booting the BBL
Description
Bad command line options were specified when booting the BBL.
Action
Specify correct command line options for booting the BBL.
See Also
tmboot(1)
18
ERROR: BBL tpsvrinit: cannot find the DBBL entry in the Bulletin Board
Description
In a networked application (MP mode), the BBL server initialization routine cannot find the DBBL entry in the Bulletin Board. The DBBL's copy of the Bulletin Board in its own process space may be corrupted.
Action
Check if the DBBL is active. The DBBL should be booted before the BBL in a networked application. Try to shut down the application, remove IPC, and then reboot the DBBL and BBL. If the error persists, contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1)
19
ERROR: BBL tpsvrinit: cannot update the DBBL entry in the Bulletin Board
Description
In a networked application (MP mode), the BBL server initialization routine cannot find the DBBL entry in the Bulletin Board. The DBBL's copy of the Bulletin Board in its own process space may be corrupted.
Action
Check if the DBBL is active. The DBBL should be booted before the BBL in a networked application. Try to shut down the application, remove IPC, and then reboot the DBBL and BBL. If the error persists, contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1)
20
ERROR: BBL tpsvrinit: cannot find the BBL entry in the Bulletin Board
Description
The BBL server initialization routine cannot find its own entry in the Bulletin Board.
Action
The Bulletin Board may be corrupted. Shut down the application, remove IPCs, and reboot the DBBL and BBL. If the error persists, contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1)
21
ERROR: BBL tpsvrinit: cannot update the BBL entry in the Bulletin Board
Description
The BBL server initialization routine cannot update its own entry in the Bulletin Board.
Action
The Bulletin Board may be corrupted. Shut down the application, remove IPC, then reboot the DBBL and BBL. If the error persists, contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1)
22
ERROR: Exceeds the maximum number of times for the BBL to get a new Bulletin Board
Description
After every interval of value in scanunit, the BBL does sanity checks on the Bulletin Board. When the BBL detects that the Bulletin Board is insane, it attempts to recover the Bulletin Board by getting a new one. When the maximum number of Bulletin Board uploads have been received, the BBL will exit.
Action
The Bulletin Board on the local machine may have been corrupted. System recovery attempts have failed. Contact your BEA TUXEDO system Technical Support.
23
ERROR: Administrative service request servicename handled by BBL failed - msg
Description
A service request handled by the BBL failed. The request could be one of tmadmin requests, tmconfig requests, tpbroadcast requests, and others.
Action
If the error is an operating system error, the Uunixerr and errno will be printed. Check the userlog for earlier messages on the problem.
24
ERROR: The BBL could not bring down a paired bridge
Description
Before the BBL can shut down, it sends a shutdown message to its paired BRIDGE and BSBRIDGE. The paired bridges could not be brought down; the shutdown message was not created due to the insufficient memory space.
Action
Contact your BEA TUXEDO system Technical Support. See LIBTUX_CAT message 683 for further explanation.
25
ERROR: The BBL could not bring down a paired bridge
Description
Before the BBL can shut down, it sends a shutdown message to its paired BRIDGE and BSBRIDGE. The paired bridges could not be brought down because sending the shutdown message to the BRIDGE process failed.
Action
Contact your BEA TUXEDO system Technical Support. See LIBTUX_CAT messages 322, 323, 324, and 325 for further explanation.
26
INFO: The BBL is exiting system
Description
The BBL process has been shut down.
Action
No action required.
See Also
tmshutdown(1)
27
ERROR: BBL bbclean: cannot re-attach to the Bulletin Board for recovery
Description
After detecting that the Bulletin Board is corrupted, the BBL failed to re-initialize and re-attach to the Bulletin Board.
Action
The Bulletin Board on your machine has been corrupted, recovery attempts have failed. Contact your BEA TUXEDO system Technical Support.
28
ERROR: BBL bbclean: cannot find the DBBL entry in the Bulletin Board
Description
The Bulletin Board cleanup process cannot find the DBBL entry in the Bulletin Board. The DBBL 's copy of the Bulletin Board in its own process space may be corrupted.
Action
Contact your BEA TUXEDO system Technical Support. See messages 18 and 19 above for further explanation.
29
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while cleaning the Bulletin Board.
Action
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.
30
ERROR: BBL bbclean cannot find BBL entries in the Bulletin Board
Description
The Bulletin Board cleanup process cannot find the BBL entry in the Bulletin Board. The Bulletin Board may be corrupted.
Action
Contact your BEA TUXEDO system Technical Support.
31
ERROR: BBL bbclean cannot find DBBL entry in the Bulletin Board
Description
The Bulletin Board cleanup process cannot find the DBBL entry in the Bulletin Board. The DBBL 's copy of the Bulletin Board in its own process space may be corrupted.
Action
Contact your BEA TUXEDO system Technical Support. See messages 18 and 19 in this chapter for further explanation.
32
ERROR: BBL bbclean cannot find queue entry for DBBL in the Bulletin Board
Description
While attempting to clean up the Bulletin Board, the cleanup process was unable to find the queue entry associated with the DBBL in its internal tables.
Action
Contact your BEA TUXEDO system Technical Support.
33
ERROR: BBL bbclean cannot open Bulletin Board image, filename while restarting the DBBL
Description
While attempting to restart the DBBL, the cleanup process cannot create a temporary file for the Bulletin Board.
Action
Check and clean up space in either $TMPDIR or /tmp on your machine, or contact your BEA TUXEDO system Technical Support.
34
ERROR: BBL bbclean cannot write the Bulletin Board for restarting the DBBL
Description
While attempting to restart the DBBL, the cleanup process was unable to write to the Bulletin Board.
Action
Check free space and file permissions either in $TMPDIR or /tmp on your machine, or contact your BEA TUXEDO system Technical Support.
36
ERROR: BBL bbclean attempting to restart the DBBL failed
Description
The cleanup process attempting to restart the DBBL failed. Possible causes: 1) remote restart failed, 2) the TUXDIR environment variable was not set, or 3) system() call failed.
Action
Check the remote connection and the TUXDIR environment variable. Also, check the error returned from system() call, or contact your BEA TUXEDO system Technical Support.
37
WARN: BBL received stray reply from the BBL's reply queue
Description
A stray reply message has appeared on the BBL reply message queue.
Action
No action required.
38
ERROR: BBL requested service service failed - errmsg
Description
The requested service handled by the BBL failed.
Action
Check the userlog for additional messages on the failure.
39
ERROR: BBL cannot find the DBBL
Description
While the BBL is handling a service request, it cannot find DBBL.
Action
Check for a partitioned network or corrupted shared memory, or contact your BEA TUXEDO system Technical Support.
40
WARN: BBL found an unexpected transaction state trans_state
Description
While the BBL is waiting for requests, it times out and performs a scan of the GTT table every scanunit seconds. An unexpected transaction state was detected in the GTT table entry of the Bulletin Board.
Action
No action required. However, the local groups participating in the transaction are notified. If the transaction is already decided, they are sent a commit request. Otherwise, an abort, timeout, or status request is sent to the TMSs.
41
WARN: BBL found unexpected flag flagval in the message
Description
While the BBL is waiting for requests, it times out and performs a scan of the GTT table every scanunit seconds. Based on the location of the groups in transaction and transaction state, a different message will be sent to groups. However, an unexpected flag was detected in the message, and thus, no message was sent to the TMSs.
Action
No action required.
42
WARN: BBL failed to wake up the blocking process - pid
Description
After checking for transaction timeout, the BBL goes through the registry table entry list and decrements the timeleft field for blocking processes. If the timeleft value becomes less than or equal to zero, the process is sent a message to be woken up. This error indicates that the BBL fails to wake up the blocking process.
Action
No action required.
43
WARN: SIGTERM was ignored while shutting down the BBL
Description
The SIGTERM signal was received and ignored while shutting down the BBL.
Action
See tmshutdown command for shutdown procedures.
See Also
tmshutdown(1)
44
ERROR: Must have a RESOURCES section
Description
The UBBCONFIG file must include a RESOURCES section.
Action
Add the RESOURCES section with appropriate values to the UBBCONFIG file.
See Also
ubbconfig(5)
45
ERROR: Must have a MACHINES section
Description
The UBBCONFIG file must include a MACHINES section.
Action
Add the MACHINES section with appropriate values to the UBBCONFIG file.
See Also
ubbconfig(5)
46
WARN: Missing GROUPS section
Description
The GROUPS section is missing in the UBBCONFIG file. This is not a fatal error since groups can be added via tmconfig.
Action
No action required if the groups will later be added via tmconfig. In most cases, a GROUPS section would exist in the UBBCONFIG file. If the GROUPS section is desired, it should be added to the UBBCONFIG file.
See Also
tmconfig(1), ubbconfig(5)
47
WARN: Missing SERVERS section
Description
The SERVERS section is missing in the UBBCONFIG file. This is not a fatal error since servers can be added via tmconfig.
Action
No action required if the servers will later be added via tmconfig. In most cases, a SERVERS section would exist in the UBBCONFIG file. If the SERVERS section is desired, it should be added to the UBBCONFIG file.
See Also
tmconfig(1), ubbconfig(5)
48
WARN: Missing SERVICES section
Description
The SERVICES section is missing in the UBBCONFIG file. This is not a fatal error since services can be added via tmconfig.
Action
No action required if the services will later be added via tmconfig. In most cases, a SERVICES section would exist in the UBBCONFIG file. If the SERVICES section is desired, it should be added to the UBBCONFIG file.
See Also
tmconfig(1), ubbconfig(5)
49
WARN: Missing NETWORK section
Description
The NETWORK section is missing in the UBBCONFIG file. This is not a fatal error since network configurations can be added via tmconfig.
Action
No action required if the network configuration will later be added via tmconfig. In most cases in which the MP model and LAN option are given, a NETWORK section would exist in the UBBCONFIG file. If the NETWORK section is desired, it should be added to the UBBCONFIG file. If the NETWORK section is not desired at all, then the LAN option and/or MP model should be checked.
See Also
tmconfig(1), ubbconfig(5)
50
ERROR: Multiple machines cannot be configured for SHM mode
Description
The option of SHM for MODEL and having multiple machines defined in the MACHINES section are mutually exclusive.
Action
Either MODEL should be set to MP in the RESOURCES section of the UBBCONFIG file, or the MACHINES section of the configuration file should have no more than one machine.
See Also
ubbconfig(5)
51
ERROR: MIGRATE option cannot be used with SHM mode
Description
The MIGRATE option in the RESOURCES section of the UBBCONFIG file cannot be used with the SHM value of MODEL also in the RESOURCES section.
Action
Either the MODEL value must be changed from SHM to MP, or MIGRATE must be removed from the OPTION values in the UBBCONFIG file.
See Also
ubbconfig(5)
53
ERROR: Can't have duplicate RESOURCES section
Description
There are multiple RESOURCES sections defined in the UBBCONFIG file.
Action
Remove the extraneous RESOURCES section from the UBBCONFIG file.
See Also
ubbconfig(5)
54
ERROR: IPCKEY must be specified in RESOURCES section
Description
The IPCKEY parameter is required to be set in the RESOURCES section of the UBBCONFIG file.
Action
Set the IPCKEY parameter in the RESOURCES section of the UBBCONFIG file.
See Also
ubbconfig(5)
55
ERROR: MASTER must be specified in RESOURCES section
Description
The MASTER parameter is required to be set in the RESOURCES section of the UBBCONFIG file.
Action
Set the MASTER parameter in the RESOURCES section of the UBBCONFIG file.
See Also
ubbconfig(5)
56
ERROR: MODEL must be specified in RESOURCES section
Description
The MODEL parameter is required to be set in the RESOURCES section of the UBBCONFIG file.
Action
Set the MODEL parameter in the RESOURCES section of the UBBCONFIG file.
See Also
ubbconfig(5)
58
ERROR: MODEL must be MP for LAN option
Description
The MODEL parameter must be set to MP (multiple processors) if the LAN option is specified in the OPTIONS parameter in the RESOURCES section of the UBBCONFIG file.
Action
If the LAN option is desired then the MODEL parameter must be set to MP in the RESOURCES section of the UBBCONFIG file. If that option is not desired, the OPTION parameter must be corrected to remove the LAN option.
See Also
ubbconfig(5)
59
ERROR: SCANUNIT (number) must be a multiple of 5, > 0 and <= 60
Description
The value for the SCANUNIT parameter in the RESOURCES section of the UBBCONFIG file must be a multiple of 5, must be greater than 0, and must be less than or equal to 60.
Action
Set the SCANUNIT parameter in the RESOURCES section of the UBBCONFIG file to a value that is a multiple of 5, greater than 0, and less than or equal to 60.
60
ERROR: SCANUNIT (value) must be a multiple of 2 or 5, > 0 and <= 60
Description
Action
65
ERROR: Identifier string must be <= len characters in length
Description
The identifier specified has a value that is greater than the specified maximum number of characters in length.
Action
Correct the length of the value of the identifier in the UBBCONFIG file to be less than or equal to the specified number of characters.
See Also
ubbconfig(5)
67
ERROR: String string - must be <= len characters in length
Description
The string specified has a length that is greater than the specified maximum number of characters.
Action
Correct the string in the UBBCONFIG file to be less than or equal to the specified number of characters.
See Also
ubbconfig(5)
70
ERROR: Identifier for MASTER must be <= len characters in length
Description
The identifier specified for MASTER in the RESOURCES section of the UBBCONFIG file has a length that is greater than the specified maximum number of characters.
Action
Correct the value for MASTER as specified in the RESOURCES section of the UBBCONFIG file to have a length less than or equal to the specified value.
See Also
ubbconfig(5)
72
ERROR: Identifier for MASTER must be <= len characters in length
Description
The identifier specified for MASTER in the RESOURCES section of the UBBCONFIG file has a length that is greater than the specified maximum number of characters.
Action
Correct the value for MASTER as specified in the RESOURCES section of the UBBCONFIG file to have a length less than or equal to the specified value.
See Also
ubbconfig(5)
73
ERROR: Invalid MASTER parameter - duplicate LMID lmidname specified
Description
A comma-separated pair of logical machine names was specified for the MASTER field value in the RESOURCES section, but both values are the same. The first logical machine name represents the configuration primary machine, and the second logical machine name represents a backup machine to which the master may be migrated; they cannot be identical.
Action
Correct the MASTER parameter such that the LMID values are unique, or don't specify a backup machine, and re-load the configuration.
See Also
ubbconfig(5)
76
ERROR: UID is not effective user ID
Description
The value for UID as specified in the RESOURCES section of the UBBCONFIG file is not the effective user id of the tmloadcf process. The effective UID of the tmloadcf process must be the same as the UID specified in the RESOURCES section of the UBBCONFIG file.
Action
Change the UID as specified in the RESOURCES section of the UBBCONFIG file to the effective UID of the user who will be running the tmloadcf command. If this change is not desired, then the tmloadcf command cannot be run by this user.
See Also
ubbconfig(5)
79
ERROR: GID is not effective group ID
Description
The value for GID as specified in the RESOURCES section of the UBBCONFIG file is not the effective group id of the tmloadcf process. The effective GID of the tmloadcf process must be the same as the GID specified in the RESOURCES section of the UBBCONFIG file.
Action
Change the GID as specified in the RESOURCES section of the UBBCONFIG file to the effective GID of the user who will be running the tmloadcf command. If this change is not desired, then the tmloadcf command cannot be run by this user.
See Also
ubbconfig(5)
81
ERROR: PERM parameter must be >= 1 and <= 0777
Description
The value for PERM (permissions) as specified in the RESOURCES section of the UBBCONFIG file is less than 1 or greater than 0777. PERM must be greater than or equal to 1 and less than or equal to 0777.
Action
Correct the value for PERM as specified in the RESOURCES section of the UBBCONFIG file to be greater than or equal to 1 and less than or equal to 0777.
See Also
ubbconfig(5)
83
ERROR: MAXACCESSERS parameter must be > 0 and < 32768
Description
The value for MAXACCESSERS as specified in the RESOURCES section of the UBBCONFIG file, is less than or equal to 0 or greater than or equal to 32768. MAXACCESSERS must be greater than 0 and less than 32768.
Action
Correct the value for MAXACCESSERS as specified in the RESOURCES section of the UBBCONFIG file to be greater than 0 and less than 32768.
See Also
ubbconfig(5)
85
ERROR: MAXSERVERS parameter must be > 0 and < 8192
Description
The value for MAXSERVERS as specified in the RESOURCES section of the UBBCONFIG file, is less than or equal to 0 or greater than or equal to 8192. MAXSERVERS must be greater than 0 and less than 8192.
Action
Correct the value for MAXSERVERS as specified in the RESOURCES section of the UBBCONFIG file to be greater than 0 and less than 8192.
See Also
ubbconfig(5)
87
ERROR: MAXSERVICES parameter must be > 0 and < 32767
Description
The value for MAXSERVICES as specified in the RESOURCES section of the UBBCONFIG file, is less than or equal to 0 or greater than or equal to 32768. MAXSERVICES must be greater than 0 and less than 32768.
Action
Correct the value for MAXSERVICES as specified in the RESOURCES section of the UBBCONFIG file to be greater than 0 and less than 32768.
See Also
ubbconfig(5)
89
ERROR: MAXGTT parameter must be >= 0 and < 32768
Description
The value for MAXGTT as specified in the RESOURCES section of the UBBCONFIG file, is less than or equal to 0 or greater than or equal to 32767. MAXGTT must be greater than 0 and less than 32767.
Action
Correct the value for MAXGTT as specified in the RESOURCES section of the UBBCONFIG file to be greater than 0 and less than 32768.
See Also
ubbconfig(5)
91
ERROR: MAXBUFTYPE parameter must be > 0 and < 32768
Description
The value for MAXBUFTYPE as specified in the RESOURCES section of the UBBCONFIG file, is less than or equal to 0 or greater than or equal to 32768. MAXBUFTYPE must be greater than 0 and less than 32768.
Action
Correct the value for MAXBUFTYPE as specified in the RESOURCES section of the UBBCONFIG file to be greater than 0 and less than 32768.
93
ERROR: MAXBUFSUBTYPE parameter must be > 0 and < 32768
Description
The value for MAXBUFSUBTYPE as specified in the RESOURCES section of the UBBCONFIG file, is less than or equal to 0 or greater than or equal to 32768. MAXBUFSUBTYPE must be greater than 0 and less than 32768.
Action
Correct the value for MAXBUFSUBTYPE as specified in the RESOURCES section of the UBBCONFIG file to be greater than 0 and less than 32768.
See Also
ubbconfig(5)
95
ERROR: Identifier for TAGENT must be <= len characters in length
Description
The identifier specified for TAGENT in the RESOURCES section of the UBBCONFIG file has a length that is greater than the specified maximum number of characters.
Action
Correct the value for TAGENT as specified in the RESOURCES section of the UBBCONFIG file to have a length less than or equal to the specified value.
See Also
ubbconfig(5)
96
ERROR: Can't have duplicate MACHINES section
Description
There are multiple MACHINES sections defined in the UBBCONFIG file.
Action
Remove the extraneous MACHINES section from the UBBCONFIG file.
See Also
ubbconfig(5)
97
ERROR: RESOURCES section must appear before MACHINES section
Description
The MACHINES section was put before the RESOURCES section in the UBBCONFIG file. There must be a RESOURCES section before the MACHINES section.
Action
Correct the UBBCONFIG file to specify the RESOURCES section before the MACHINES section.
See Also
ubbconfig(5)
98
ERROR: lmidname specified in MASTER, but not defined in MACHINES section
Description
The identified machine was specified as the primary value of MASTER in the RESOURCES section of the UBBCONFIG file, but the machine was not defined in the MACHINES section.
Action
Add the identified machine to the MACHINES section of the UBBCONFIG file, or properly list a defined machine as the primary in the MASTER parameter in the RESOURCES section.
See Also
ubbconfig(5)
99
ERROR: lmidname specified in MASTER, but not defined in MACHINES section
Description
The identified machine was specified as the alternate value of MASTER in the RESOURCES section of the UBBCONFIG file, but the machine was not defined in the MACHINES section.
Action
Add the identified machine to the MACHINES section of the UBBCONFIG file, or properly list a defined machine as the secondary in the MASTER parameter in the RESOURCES section.
See Also
ubbconfig(5)
 |
 |
 |