CMDTUX
MESSAGES 100-199
103
ERROR: duplicate address name machinename
DESCRIPTION
The
identified address name is a duplicate in the *MACHINES section of the
UBBCONFIG file. Each machine name can only be specified once.
ACTION
Remove
the duplicate machine address name from the *MACHINES section of the UBBCONFIG
file.
SEE ALSO
ubbconfig
(5)
104
ERROR: Memory allocation failure
DESCRIPTION
An
attempt to dynamically allocate memory from the operating system using malloc
() failed while allocating space for the machine as specified in the *MACHINES
section of the UBBCONFIG file.
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.
SEE ALSO
ubbconfig
(5) and malloc (3) in UNIX System reference manuals
107
ERROR: Memory allocation failure
DESCRIPTION
An
attempt to dynamically allocate memory from the operating system using malloc
() failed while allocating space for the machine as specified in the *MACHINES
section of the UBBCONFIG file.
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.
SEE ALSO
ubbconfig (5) and malloc (3) in UNIX
System reference manuals
109
ERROR: Memory allocation failure
DESCRIPTION
An
attempt to dynamically allocate memory from the operating system using malloc
() failed while allocating space for the machine as specified in the *MACHINES
section of the UBBCONFIG file.
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.
SEE ALSO
ubbconfig
(5) and malloc (3) in UNIX System reference manuals
110
ERROR: TUXCONFIG must be specified for machine entry machinename
DESCRIPTION
The
TUXCONFIG parameter is missing from the parameters of the specified machine in
the *MACHINES section of the UBBCONFIG file. TUXCONFIG is required to be set
for each machine.
ACTION
Add
the proper TUXCONFIG parameter for the specified machine in the *MACHINES
section of the UBBCONFIG file.
SEE ALSO
ubbconfig
(5)
111
ERROR: TUXCONFIG (string) of machine machinename must be the same
as the TUXCONFIG environment variable (string)
DESCRIPTION
The
value of the TUXCONFIG parameter for the specified machine as listed in the
*MACHINES section of the UBBCONFIG file is not the same as the current value of
the TUXCONFIG environment variable. The TUXCONFIG parameter and the TUXCONFIG
environment variable are required to be the same.
ACTION
Correct
the value of the TUXCONFIG parameter of the specified machine in the *MACHINES
section of the UBBCONFIG file and/or the value of the TUXCONFIG environment
variable such that the two values are the same.
SEE ALSO
ubbconfig
(5)
112
ERROR: TUXOFFSET environment variable is unset, TUXOFFSET (offset) of
machine machinename should be zero.
DESCRIPTION
The
TUXOFFSET environment variable is not set. This implies an offset of zero. The
TUXOFFSET environment variable must match the TUXOFFSET setting in the
UBBCONFIG file if it is set. The TUXOFFSET of the specified machine is not zero
in the *MACHINES section of the UBBCONFIG file.
ACTION
Set
the TUXOFFSET of the specified machine in the *MACHINES section of the
UBBCONFIG file to match the TUXOFFSET environment variable. In the case of an
unset TUXOFFSET environment variable, it must be zero. If another value is
desired, both the TUXOFFSET in the UBBCONFIG file and the TUXOFFSET environment
variable must be set to that value.
SEE ALSO
ubbconfig
(5)
113
ERROR: APPDIR must be specified for machine entry machinename
DESCRIPTION
The
APPDIR parameter is required to be set for the specified machine in the
*MACHINES section of the UBBCONFIG file.
ACTION
Set
the APPDIR parameter for the specified machine in the *MACHINES section of the
UBBCONFIG file.
SEE ALSO
ubbconfig
(5)
114
ERROR: TUXDIR must be specified for machine entry machinename
DESCRIPTION
The
TUXDIR parameter is required to be set for the specified machine in the
*MACHINES section of the UBBCONFIG file.
ACTION
Set
the TUXDIR parameter for the specified machine in the *MACHINES section of the
UBBCONFIG file.
SEE ALSO
ubbconfig
(5)
116
ERROR: Machine machinename must be <= len characters in length
DESCRIPTION
The
machine name specified in the *MACHINES section of the UBBCONFIG file is longer
than the specified maximum number of characters.
ACTION
Correct
the machine name as specified in the *MACHINES section of the UBBCONFIG file to
have a length less than or equal to the specified value.
SEE ALSO
ubbconfig
(5)
118
ERROR: Machine machinename must be <= len characters in length
DESCRIPTION
The
machine name specified in the *MACHINES section of the UBBCONFIG file is longer
than the specified maximum number of characters.
ACTION
Correct
the machine name as specified in the *MACHINES section of the UBBCONFIG file to
have a length less than or equal to the specified value.
SEE ALSO
ubbconfig
(5)
120
ERROR: Machine machinename must be <= len characters in length
DESCRIPTION
The
machine name specified in the *MACHINES section of the UBBCONFIG file is longer
than the specified maximum number of characters.
ACTION
Correct
the machine name as specified in the *MACHINES section of the UBBCONFIG file to
have a length less than or equal to the specified value.
SEE ALSO
ubbconfig
(5)
122
ERROR: LMID lmidname must be <= len characters in length
DESCRIPTION
The
logical machine id (LMID) as specified in the UBBCONFIG file is longer than the
specified maximum number of characters.
ACTION
Correct
the logical machine id (LMID) as specified in the UBBCONFIG file to have a
length less than or equal to the specified value.
SEE ALSO
ubbconfig
(5)
124
ERROR: LMID lmidname must be <= len characters in length
DESCRIPTION
The
logical machine id (LMID) as specified in the UBBCONFIG file is longer than the
specified maximum number of characters.
ACTION
Correct
the logical machine id (LMID) as specified in the UBBCONFIG file to have a
length less than or equal to the specified value.
SEE ALSO
ubbconfig
(5)
126
ERROR: TUXCONFIG must be an absolute pathname
DESCRIPTION
The
value for the TUXCONFIG parameter as specified in the *MACHINES section of the
UBBCONFIG file must be an absolute pathname. Relative paths and environment variables
are not valid.
ACTION
Correct
the value for TUXCONFIG as specified in the *MACHINES section of the UBBCONFIG
file to be an absolute pathname.
SEE ALSO
ubbconfig
(5)
128
ERROR: Identifier for TUXCONFIG must be <= len characters in length
DESCRIPTION
The
identifier for TUXCONFIG as specified in the *MACHINES section of the UBBCONFIG
file is longer than the specified maximum number of characters.
ACTION
Correct
the value of TUXCONFIG as specified in the *MACHINES section of the UBBCONFIG
file to have a length less than or equal to the specified value.
SEE ALSO
ubbconfig
(5)
130
ERROR: TUXDIR must be an absolute pathname
DESCRIPTION
The
value for the TUXDIR parameter as specified in the *MACHINES section of the
UBBCONFIG file must be an absolute pathname. Relative paths and environment
variables are not valid.
ACTION
Correct
the value for TUXDIR as specified in the *MACHINES section of the UBBCONFIG
file to be an absolute pathname.
SEE ALSO
ubbconfig
(5)
132
ERROR: APPDIR must be an absolute pathname
DESCRIPTION
The
value for the APPDIR parameter as specified in the *MACHINES section of the
UBBCONFIG file must be an absolute pathname. Relative paths and environment
variables are not valid.
ACTION
Correct
the value for APPDIR as specified in the *MACHINES section of the UBBCONFIG
file to be an absolute pathname.
SEE ALSO
ubbconfig
(5)
134
ERROR: TYPE parameter must be <= len characters in length
DESCRIPTION
The
value for the TYPE parameter as specified in the *MACHINES section of the
UBBCONFIG file is longer than the specified maximum number of characters.
ACTION
Correct
the value of TYPE as specified in the *MACHINES section of the UBBCONFIG file
to have a length less than or equal to the specified value.
SEE ALSO
ubbconfig
(5)
136
ERROR: Identifier for TLOGDEVICE must be <= len characters in length
DESCRIPTION
The
identifier for TLOGDEVICE as specified in the *MACHINES section of the
UBBCONFIG file is longer than the specified maximum number of characters.
ACTION
Correct
the value of TLOGDEVICE as specified in the *MACHINES section of the UBBCONFIG
file to have a length less than or equal to the specified value.
SEE ALSO
ubbconfig
(5)
138
ERROR: TUXOFFSET parameter must be >= 0
DESCRIPTION
The
value for TUXOFFSET as specified in the *MACHINES section of the UBBCONFIG
file, is less than zero. TUXOFFSET must be equal to or greater than zero.
ACTION
Correct
the value for TUXOFFSET as specified in the *MACHINES section of the UBBCONFIG
file to be greater than or equal to zero.
SEE ALSO
ubbconfig
(5)
140
ERROR: TLOGOFFSET parameter must be >= 0
DESCRIPTION
The
value for TLOGOFFSET indicated by the arrow is less than 0.
ACTION
Specify
a value for TLOGOFFSET that is greater than or equal to 0.
142
ERROR: Identifier for TLOGNAME must be <=len characters in length
DESCRIPTION
The
value for TLOGNAME indicated by the arrow is greater than 30, the number value
specified by the parameter MAXTIDENT .
ACTION
Specify
a value for TLOGNAME that has a number of characters less than or equal to the
value of MAXTIDENT .
144
ERROR: TLOGSIZE parameter must be > 0 and <= 2048
DESCRIPTION
The
value for TLOGSIZE indicated by the arrow is less than 0 or greater than 2048.
ACTION
Specify
a value for TLOGSIZE that is between 0 and 2048.
146
ERROR: ULOGPFX parameter must be an absolute pathname
DESCRIPTION
The
value for the parameter ULOGPFX indicated by the arrow is not an absolute
pathname.
ACTION
Specify
a value for ULOGPFX that is an absolute pathname, meaning it must begin with a
"/" character.
148
ERROR: ENVFILE parameter must be an absolute pathname
DESCRIPTION
The
value for the parameter ENVFILE indicated by the arrow is not an absolute pathname.
ACTION
Specify
a value for ENVFILE that is an absolute pathname, meaning it must begin with a
"/" character.
149
ERROR: Duplicate *GROUPS section
DESCRIPTION
More
than one *GROUPS section has been specified in the configuration file.
ACTION
Modify
the configuration file so that only one *GROUPS section is specified.
SEE ALSO
ubbconfig
(5)
150
ERROR: *MACHINES section must be specified before *GROUPS section
DESCRIPTION
The
*GROUPS section has been specified before the *MACHINES section in the
configuration file.
ACTION
Modify
the configuration file such that the *MACHINES section is specified before the
*GROUPS section.
SEE ALSO
ubbconfig
(5)
152
ERROR: Identifier for group name must be <= len characters in length
DESCRIPTION
The
value of the group name identifier indicated by the arrow is greater than 30
characters in the configuration file.
ACTION
Specify
a value for a group name identifier that is 30 characters or less in the
configuration file.
SEE ALSO
ubbconfig
(5)
154
ERROR: grpname defined as a LMID and it can't be a group name
DESCRIPTION
The
value for the grpname indicated by the arrow is specified as an LMID in
the configuration file.
ACTION
Specify
a value for the grpname that is unique from all the LMID values in the
configuration file.
SEE ALSO
ubbconfig
(5)
156
ERROR: Duplicate *GROUPS entry grpname
DESCRIPTION
The
value for the grpname indicated by the arrow is invalid due to being
specified previously in the *GROUPS section of the configuration file.
ACTION
Specify
a value for grpname that has not already been specified in the *GROUPS
section of the configuration file.
SEE ALSO
ubbconfig
(5)
157
ERROR: Memory allocation failure
DESCRIPTION
An
attempt to dynamically allocate memory from the operating system using malloc()
failed while setting up a table to keep track of the information kept in the
SERVERS section of the UBBCONFIG file.
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.
160
ERROR: Memory allocation failure
DESCRIPTION
An
attempt to dynamically allocate memory from the operating system using malloc()
failed while setting up a table to keep track of the information kept in the
SERVERS section of the UBBCONFIG file.
ACTION
Please
refer to Message 157 above.
161
ERROR: Must have a GRPNO on *GROUPS entry grpname
DESCRIPTION
The
value for the GRPNO parameter of the grpname indicated by the arrow is
omitted from the configuration file.
ACTION
Specify
a value for the GRPNO of the grpname.
SEE ALSO
ubbconfig
(5)
162
ERROR: Must specify LMID on *GROUPS entry group_name
DESCRIPTION
The
LMID parameter was omitted from the *GROUPS section of the configuration file.
ACTION
Edit
the configuration file so that it contains an LMID parameter.
SEE ALSO
ubbconfig
(5)
163
ERROR: Memory allocation failure
DESCRIPTION
An
attempt to dynamically allocate memory from the operating system using malloc()
failed while setting up storage to keep track of LMID names.
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.
166
ERROR: Logical machine machine_name not defined in the *MACHINES section
DESCRIPTION
The
value for the machine_name indicated by the arrow is specified in the
*GROUPS section but not defined in the *MACHINES section of the configuration
file.
ACTION
Specify
a value for the machine_name that is already defined in the *MACHINES
section, or define a logical machine for this name.
SEE ALSO
ubbconfig
(5)
167
ERROR: Memory allocation failure
DESCRIPTION
An
attempt to dynamically allocate memory from the operating system using malloc()
failed while setting up storage to keep track of LMID names.
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.
169
ERROR: Logical machine machine_name not defined in *MACHINES section
DESCRIPTION
The
value for the machine_name indicated by the arrow is specified in the
*GROUPS section but not defined in the *MACHINES section of the configuration
file.
ACTION
Specify
a value for the machine_name that is already defined in the *MACHINES
section, or define a logical machine for this name.
SEE ALSO
ubbconfig
(5)
171
ERROR: Logical machine machine_name not defined in *MACHINES section
DESCRIPTION
The
value for the machine_name indicated by the arrow is specified in the
*GROUPS section but not defined in the *MACHINES section of the configuration
file.
ACTION
Specify
a value for the machine_name that is already defined in the *MACHINES
section, or define a logical machine for this name.
SEE ALSO
ubbconfig
(5)
172
ERROR: Duplicate LMID machine_name specified in group entry group_name
DESCRIPTION
The
same LMID value was used twice within a logical group name in the *GROUPS
section of the configuration file.
ACTION
Edit
the configuration file such that each LMID value is unique within a logical
group name.
SEE ALSO
ubbconfig
(5)
174
ERROR: TMSNAME parameter must be <= len characters in length
DESCRIPTION
The
value for TMSNAME indicated by the arrow is greater than 78 characters.
ACTION
Specify
a value for TMSNAME that is less than or equal to 78 characters in length.
SEE ALSO
ubbconfig
(5)
176
ERROR: TMSCOUNT parameter must be > 1 and <= 10
DESCRIPTION
The
value for TMSCOUNT indicated by the arrow is less than 2 or greater than 10.
ACTION
Specify
a value for TMSCOUNT that is greater than or equal to 2 but less than or equal
to 10.
SEE ALSO
ubbconfig
(5)
178
ERROR: CLOSEINFO parameter must be <= len characters in length
DESCRIPTION
The
value for the CLOSEINFO string indicated by the arrow is greater than 256
characters.
ACTION
Specify
a value for the CLOSEINFO string that is less than or equal to 256 characters
in length.
SEE ALSO
ubbconfig
(5)
180
ERROR: OPENINFO parameter must be <= len characters in length
DESCRIPTION
The
value for the OPENINFO string indicated by the arrow is greater than 256
characters in length.
ACTION
Specify
a value for the OPENINFO string that is less than or equal to 256 characters in
length.
SEE ALSO
ubbconfig
(5)
182
ERROR: GRPNO parameter must be < number and > 0
DESCRIPTION
The
value for GRPNO indicated by the arrow is less than 0 or greater than or equal
to 30,000.
ACTION
Specify
a value for GRPNO that is greater than 0 and less than 30,000.
SEE ALSO
ubbconfig
(5)
184
ERROR: *GROUPS entry grpname has a duplicate GRPNO parameter of group_number
DESCRIPTION
The
grpname entry in the *GROUPS section of the configuration file has a
GRPNO value of group_number that is the same as another entry in the
section.
ACTION
Specify
a unique GRPNO value for the grpname.
SEE ALSO
ubbconfig
(5)
186
ERROR: Duplicate *SERVERS section
DESCRIPTION
More
than one SERVERS section has been defined in the configuration file.
ACTION
Edit
the configuration file such that there is only one SERVERS section defined.
SEE ALSO
ubbconfig
(5)
187
ERROR: *GROUPS section must appear before *SERVERS section
DESCRIPTION
The
SERVERS section has been defined before the *GROUPS section in the
configuration file.
ACTION
Edit
the configuration file such that the *RESOURCES, *MACHINES, and *GROUPS
sections are the first three sections in that order.
SEE ALSO
ubbconfig
(5)
188
ERROR: SRVGRP parameter missing in *SERVERS entry AOUT
DESCRIPTION
Each
entry in the SERVERS section of the configuration file must have a SRVGRP
parameter.
ACTION
Specify
a SRVGRP value that specifies the group name for the group in which the server
is to run.
SEE ALSO
ubbconfig
(5)
189
ERROR: SRVID parameter missing in *SERVERS entry
DESCRIPTION
Each
entry in the SERVERS section of the configuration file must have a SRVID
parameter.
ACTION
Specify
a SRVID value that specifies an integer that uniquely identifies a server
within a group.
SEE ALSO
ubbconfig
(5)
190
ERROR: SRVID number is not unique among server group groupname
DESCRIPTION
The
specified SRVID number parameter number has already been used in a
SERVERS section entry of the configuration file.
ACTION
Specify
a SRVID value that specifies an integer that uniquely identifies a server
within a group.
SEE ALSO
ubbconfig
(5)
191
ERROR: Memory allocation failure
DESCRIPTION
An
attempt to dynamically allocate memory from the operating system using malloc()
failed while setting up a table to keep track of the information kept in the
SERVERS section of the UBBCONFIG file.
ACTION
Please
refer to Message 157 above.
192
ERROR: Memory allocation failure
DESCRIPTION
An
attempt to dynamically allocate memory from the operating system using malloc()
failed while setting up a table to keep track of the information kept in the
SERVERS section of the UBBCONFIG file.
ACTION
Please
refer to Message 157 above.
193
ERROR: RQADDR request_queue_name can't be defined for SRVGRP grpname1
and grpname2
DESCRIPTION
The
same RQADDR parameter value has been specified for use in two different server
groups entries in the SERVERS section of the configuration file.
ACTION
Edit
the configuration file such that if the same RQADDR is used, then both servers
have the SRVGRP value. Otherwise, assign different RQADDR values to the
servers.
194
ERROR: Server svrname1 and svrname2 can't share the same RQADDR rqaddr.
DESCRIPTION
The
same RQADDR was defined for two servers which are not in the same server group.
ACTION
Check
and edit the UBBCONFIG file such that either two different RQADDR s are used
for each server or that both servers are on the same server group.
198
ERROR: Memory allocation failure
DESCRIPTION
An
attempt to dynamically allocate memory from the operating system using malloc
() failed while setting up a table to keep track of the information kept in the
SERVERS section of the UBBCONFIG file.
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.
199
ERROR: Memory allocation failure
DESCRIPTION
An
attempt to dynamically allocate memory from the operating system using malloc()
failed while setting up a table to keep track of the information kept in the
SERVERS section of the UBBCONFIG file.
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.
CMDTUX
MESSAGES 200-299
201
ERROR: CLOPT parameter must be <= len characters in length
DESCRIPTION
The
value for CLOPT indicated by the arrow is greater than 256 characters in
length.
ACTION
Edit
the configuration file such that all CLOPT parameters are less than or equal to
256 characters.
SEE ALSO
ubbconfig
(5)
203
ERROR: Group name must be <= len characters in length
DESCRIPTION
The
SRVGRP value indicated by the arrow is greater than 30 characters in length.
ACTION
Edit
the configuration file such that all SRVGRP values are less than or equal to 30
characters in length.
SEE ALSO
ubbconfig
(5)
205
ERROR: Group name grpname not defined in *GROUPS section
DESCRIPTION
The
specified server group name grpname has not been defined in the *GROUPS
section of the configuration file.
ACTION
Edit
the configuration file such that the server group name is defined in the
*GROUPS section.
SEE ALSO
ubbconfig
(5)
207
ERROR: SRVID parameter must be >= 1 and <= 30000
DESCRIPTION
The
value for SRVID indicated by the arrow must be greater than or equal to 1 and
less than or equal to 30000.
ACTION
Specify
a value for SRVID that is greater than or equal to 1 and less than or equal to
30000.
SEE ALSO
ubbconfig
(5)
209
ERROR: RQADDR parameter must be <= len characters in length
DESCRIPTION
The
value for RQADDR indicated by the arrow must be less than or equal to 30
characters in length.
ACTION
Specify
a value for RQADDR that is less than 31 characters in length.
SEE ALSO
ubbconfig
(5)
211
ERROR: RQPERM parameter must be >= 1 and <= 0777
DESCRIPTION
The
value for RQPERM indicated by the arrow must be between 0001 and 0777,
inclusive.
ACTION
Specify
a value for RQPERM that is between 0001 and 0777, inclusive.
SEE ALSO
ubbconfig
(5)
213
ERROR: RPPERM parameter must be >=1 and <= 0777
DESCRIPTION
The
value for RPPERM indicated by the arrow must be between 0001 and 0777,
inclusive.
ACTION
Specify
a value for RPPERM that is between 0001 and 0777, inclusive.
SEE ALSO
ubbconfig
(5)
215
ERROR: MAXGEN parameter must be >= 1 and < 256
DESCRIPTION
The
value given for MAXGEN indicated by the arrow is invalid because it is not
between 1 and 255, inclusive.
ACTION
Specify
a value for MAXGEN that is between 1 and 255, inclusive.
SEE ALSO
ubbconfig
(5)
217
ERROR: GRACE parameter must be >= 0
DESCRIPTION
The
value for GRACE indicated by the arrow is invalid because it is not greater
than or equal to 0.
ACTION
Specify
a value for GRACE that is greater than or equal to 0.
SEE ALSO
ubbconfig
(5)
219
ERROR: SEQUENCE parameter must be > 0 and < 10000
DESCRIPTION
The
value given for SEQUENCE indicated by the arrow is invalid because it is not
between 1 and 9999, inclusive.
ACTION
Specify
a value for SEQUENCE that is between 1 and 9999, inclusive.
SEE ALSO
ubbconfig
(5)
220
ERROR: Duplicate *SERVICES section
DESCRIPTION
There
is more than one SERVICES section of the configuration file defined.
ACTION
Edit
the configuration file such that there is only one SERVICES section.
SEE ALSO
ubbconfig
(5)
221
ERROR: *GROUPS section must appear before *SERVICES section
DESCRIPTION
The
SERVICES section is defined before the *GROUPS section in the configuration file.
ACTION
Edit
the configuration file such that the *GROUPS section is defined before the
SERVICES section.
SEE ALSO
ubbconfig
(5)
222
ERROR: Could not initialize sort of *SERVICES section
DESCRIPTION
An
internal error occurred while attempting to sort the SERVICES section during
tmloadcf .
ACTION
Attempt
to load the configuration again via tmloadcf . If the error occurs again,
contact TUXEDO System Technical Support.
SEE ALSO
ubbconfig
(5), tmloadcf (1)
223
ERROR: Could not turnaround sort of *SERVICES section
DESCRIPTION
An
internal error occurred while attempting to sort the SERVICES section of the
configuration file during tmloadcf .
ACTION
Attempt
to load the configuration again via tmloadcf . If the error occurs again,
contact TUXEDO System Technical Support.
SEE ALSO
ubbconfig
(5), tmloadcf (1)
224
ERROR: Couldn't retrieve data from *SERVICES sort
DESCRIPTION
An
internal error occurred while attempting to sort the SERVICES section of the
configuration file during tmloadcf .
ACTION
Attempt
to load the configuration again via tmloadcf . If the error occurs again,
contact TUXEDO System Technical Support.
SEE ALSO
ubbconfig
(5), tmloadcf (1)
226
ERROR: Service name must be <= len characters in length
DESCRIPTION
The
SVCNM parameter indicated by the arrow is invalid because it is more than 15
characters in length.
ACTION
Specify
a service name value that is less than or equal to 15 characters in length.
SEE ALSO
ubbconfig
(5)
228
ERROR: Service service_name can't have two different ROUTING values
DESCRIPTION
The
indicated service name has two different routing criteria associated with it.
ACTION
Edit
the configuration file such that if multiple ROUTING entries exist for the same
service name but have different SRVGRP parameters, the ROUTING parameter must
be the same for all of these entries.
SEE ALSO
ubbconfig
(5)
229
ERROR: Memory allocation failure
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using malloc
() failed while setting up a table to keep track of the information kept in the
SERVERS section of the UBBCONFIG file.
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.
230
ERROR: Memory allocation failure
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using malloc
() failed while setting up a table to keep track of the information kept in the
SERVICES section of the UBBCONFIG file.
ACTION
Please
refer to message 229 above.
231
ERROR: Memory allocation failure
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using malloc
() failed while setting up a table to keep track of the information kept in the
SERVICES section of the UBBCONFIG file.
ACTION
Please
refer to message 229 above.
232
ERROR: Need different SRVGRP for the SERVICE svcname.
DESCRIPTION
The
same service has been specified more than once, but the SRVGRP parameter is
absent.
ACTION
Edit
the UBBCONFIG file and specify different SRVGRP entries for each SVCNAME
defined.
SEE ALSO
ubbconfig
(5)
233
ERROR: SERVICE svcname can't have SRVGRP srvgrp on different entry.
DESCRIPTION
The
same service has been specified more than once, using the same SRVGRP value.
ACTION
Edit
the UBBCONFIG file and specify different SRVGRP entries for each SVCNAME
defined.
SEE ALSO
ubbconfig
(5)
235
ERROR: Memory allocation failure
DESCRIPTION
The
tmloadcf command uses the malloc () library call to obtain the internal memory
that it uses for parsing the configuration file. One of these malloc () calls
failed, meaning that no memory was available. It is possible that the
configuration file was too large on a machine with a limited amount of free
memory or swap space.
ACTION
Try
running tmloadcf again when the machine is less heavily loaded. Try reducing
the size of the configuration file by making use of the DEFAULT parameters to
set global options for each section.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
237
ERROR: Failure during input to sort of *SERVICES section
DESCRIPTION
The
tmloadcf command sorts the entries in the SERVICES section by service name.
During this processing, an internal error occurred. Since sort processing uses
temporary memory and disk space, the most common cause of sort failure is if
these resources run out. The temporary files used for sorting are usually
placed in /usr/tmp or /tmp .
ACTION
Check
that there is available temporary disk space in /usr/tmp and /tmp . Try running
the command again when the system is less heavily loaded.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
239
ERROR: The SRVGRP parameter must be <= len characters
DESCRIPTION
The
SRVGRP parameter in the configuration file must be a string of 30 or fewer
characters.
ACTION
Choose
a SRVGRP value that is no more than 30 characters and make sure it matches a
group name in the *GROUPS section.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
241
ERROR: Group name group_name must match a name from the *GROUPS section
DESCRIPTION
The
SRVGRP parameter of the SERVERS section in the configuration file does not
match an entry in the *GROUPS section. This can be due to a direct error here,
or a previous error while compiling the group name entry.
ACTION
Correct
the SRVGRP entry, or the group name entry that it is supposed to match.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
243
ERROR: BUFTYPE parameter must be <= len characters
DESCRIPTION
The
BUFTYPE parameter in the configuration file must be a string of 256 or fewer
characters.
ACTION
Shorten
the BUFTYPE parameter, and make sure it matches a buffer type that is in the
TUXEDO System Type-Switch.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
245
ERROR: TRANTIME parameter must be >= 0 and < 2147483648
DESCRIPTION
The
TRANTIME parameter was outside the allowable numeric range.
ACTION
Specify
a value that is 0 or greater and less than 2,147,483,648.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
247
ERROR: *ROUTING routingname must be <= len characters
DESCRIPTION
The
routingname of the ROUTING section of the configuration file must be
<= 15 characters.
ACTION
Specify
a value that is less than or equal to 15 characters.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
249
ERROR: LOAD parameter must be >= 1 and <= 32767
DESCRIPTION
The
LOAD parameter in the SERVICES section of the configuration file must be within
the proper range of values.
ACTION
Specify
a value that is between 1 and 32,767.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
251
ERROR: PRIO parameter must be >= 1 and <= 100
DESCRIPTION
The
PRIO parameter in the SERVICES section of the UBBCONFIG must be within the
proper range of values.
ACTION
Specify
a value that is between 1 and 100, inclusive.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
252
ERROR: Duplicate *ROUTING section present
DESCRIPTION
A
second ROUTING section was encountered in the configuration file. Only one is
allowed.
ACTION
Place
all routing entries within a single ROUTING section.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
253
ERROR: The *GROUPS section must appear before the *ROUTING section
DESCRIPTION
The
ROUTING section appeared in the configuration file before any *GROUPS section
appeared. This could be due to the sections being out of order or missing.
ACTION
Make
sure that the *GROUPS section appears before the ROUTING section.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
255
ERROR: Routing name must be <= len characters
DESCRIPTION
The
ROUTING identifier must be <= 15 characters.
ACTION
Specify
a value that is less than or equal to 15 characters.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
256
ERROR: FIELD parameter missing in *ROUTING entry routingname
DESCRIPTION
Each
entry in the ROUTING section of the configuration file must have a FIELD
parameter.
ACTION
Specify
a FIELD value for each entry that is the name of the routing field.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
257
ERROR: RANGES parameter missing in *ROUTING entry routingname
DESCRIPTION
Each
entry in the ROUTING section of the configuration file must have a RANGES
parameter.
ACTION
Specify
a RANGES value for each entry that specifies the ranges and associated server
groups for the routing field.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
258
ERROR: BUFTYPE parameter missing in *ROUTING entry routingname
DESCRIPTION
Each
entry in the ROUTING section of the configuration file must have a BUFTYPE
parameter.
ACTION
Specify
a BUFTYPE value that is a list of types and subtypes of data buffers for which
this routing entry is valid.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
260
ERROR: FIELD parameter must be <= len characters in length
DESCRIPTION
The
Field name in the ROUTING section must be less than 30 characters in length.
ACTION
Specify
a FIELD name that is less than 30 characters long.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
262
ERROR: RANGES parameter must be <= len characters
DESCRIPTION
The
RANGES string in the ROUTING section was greater than 256 characters in length.
ACTION
Shorten
the RANGES string and re-load the configuration file.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
264
ERROR: BUFTYPE parameter must be <= len characters
DESCRIPTION
The
BUFTYPE parameter was greater than 256 characters.
ACTION
Shorten
the BUFTYPE parameter and re-load the configuration file.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
265
ERROR: More than one NETWORK section is present
DESCRIPTION
A
UBBCONFIG file can only have one *NETWORK section. More than one *NETWORK
section was encountered while processing the UBBCONFIG file.
ACTION
Check
the UBBCONFIG file for the *NETWORK keyword. It is possible that an editing
error left an extra copy of that line.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
266
ERROR: The *MACHINES section must precede the *NETWORK section
DESCRIPTION
The
*NETWORK section of the UBBCONFIG file was encountered before any *MACHINES
section. The information in the *MACHINES section is needed to process the
*NETWORK section.
ACTION
Check
if a *MACHINES section is in the UBBCONFIG file. If it is, place it before the
*NETWORK section.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
272
ERROR: *NETWORK LMID lmid does not appear in *MACHINES section
DESCRIPTION
The
LMID identifier lmid in the *NETWORK section of the UBBCONFIG file did
not appear in the *MACHINES section. The LMID parameter is the identifier at
the beginning of the line, and does not appear with the keyword LMID .
ACTION
Make
sure that the LMID is spelled correctly, and has a matching entry in the
*MACHINES section.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
274
ERROR: NADDR parameter missing in *NETWORK entry lmid
DESCRIPTION
The
entry for lmid in the *NETWORK section has no NADDR parameter. This
parameter is required.
ACTION
Add
a NADDR parameter to the *NETWORK entry.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
276
ERROR: NADDR parameter must be <= len characters in length
DESCRIPTION
The
NADDR parameter in the *NETWORK section of the UBBCONFIG file must be <= len
characters.
ACTION
Shorten
the NADDR parameter and re-load the configuration.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
278
ERROR: There is an invalid hexadecimal digit in the NADDR parameter
DESCRIPTION
The
NADDR parameter in the *NETWORK section of the UBBCONFIG file was specified as
a hexadecimal number (starting with 0x or \x), but a non-hexadecimal character
was encountered in the string.
ACTION
Enter
hexadecimal characters in the NADDR parameter and re-load the configuration.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
280
ERROR: NADDR parameter must contain an even number of hex digits.
DESCRIPTION
The
NADDR parameter in the *NETWORK section of the UBBCONFIG file was specified as
a hexadecimal number (starting with 0x or \x). This requires that there be an
even number of characters following the prefix.
ACTION
Correct
the NADDR to have an even number of hexadecimal characters and re-load the
configuration.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
282
ERROR: BRIDGE parameter must be an absolute pathname
DESCRIPTION
The
BRIDGE parameter in the *NETWORK section of the UBBCONFIG file must be an
absolute pathname of the network device. This means it must begin with a '/'
character.
ACTION
Replace
the current BRIDGE parameter with the full pathname of the device, for example,
"/dev/tcp".
SEE ALSO
tmloadcf
(1), ubbconfig (5)
284
ERROR: NLSADDR parameter must be <= len characters
DESCRIPTION
The
NLSADDR parameter in the *NETWORK section of the UBBCONFIG file must be <= len
characters.
ACTION
Change
the NLSADDR parameter to be 78 characters or less and reload the configuration.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
286
ERROR: There is an invalid hexadecimal digit in the NLSADDR parameter
DESCRIPTION
The
NLSADDR parameter in the *NETWORK section of the UBBCONFIG file was specified
as a hexadecimal number (starting with 0x or \x), but a non-hexadecimal
character was encountered in the string.
ACTION
Enter
hexadecimal characters in the NLSADDR parameter and re-load the configuration.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
288
ERROR: NLSADDR parameter must contain an even number of hex digits
DESCRIPTION
The
NLSADDR parameter in the *NETWORK section of the UBBCONFIG file was specified
as a hexadecimal number (starting with 0x or \x). This requires that there be
an even number of characters following the prefix.
ACTION
Correct
the NLSADDR to have an even number of hexadecimal characters and re-load the
configuration.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
290
ERROR: NETID parameter must be >=0 and <=256
DESCRIPTION
The
NETID is an undocumented parameter in the UBBCONFIG file, used for internal
testing purposes. It should not be used by the end user.
ACTION
Remove
the NETID parameter or change its value to be in the range 1-255.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
291
ERROR: Failure opening TUXCONFIG section sectionname (vtoc_error=vtoc_errno)
DESCRIPTION
The
TUXCONFIG file is a binary file in the TUXEDO VTOC format. Each section of the
UBBCONFIG file (*RESOURCES, *MACHINES, etc.) is stored as a separate table in
the TUXCONFIG file. While trying to update the TUXCONFIG file, tmloadcf got an
error trying to open the specified sectionname. The section of the
TUXCONFIG , and a low level error code, are printed in this message.
ACTION
If
the TUXCONFIG VTOC is only being used to hold the TUXCONFIG tables (and not the
TLOG or a TUXEDO/D database), then the first thing to try is to recreate a new
TUXCONFIG. If the TUXCONFIG is a UNIX file, simply remove it. If it is stored
on a raw disk, erase it by doing: echo "" >$TUXCONFIG If the error
persists, check for disk-type error conditions that might cause problems
writing to files. Finally, contact TUXEDO System Technical Support, making sure
to have the vtoc_errno that was printed in the error message.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
292
ERROR: Error writing *RESOURCES section of the TUXCONFIG file (vtoc_errno= vtoc_errno)
DESCRIPTION
The
TUXCONFIG file is a binary file in the TUXEDO VTOC format. Each section of the
UBBCONFIG file (*RESOURCES, *MACHINES, etc.) is stored as a separate table in
the TUXCONFIG file. An error occurred while trying to write to the *RESOURCES
section of the TUXCONFIG .
ACTION
If
the TUXCONFIG file is a UNIX file, the file system that it is in should be
checked to see if it has enough free space. The file should be checked to see
if its permissions allow writing. If the TUXCONFIG VTOC is only being used to
hold the TUXCONFIG tables (and not the TLOG or a TUXEDO/D database), then the
first thing to try is to recreate a new TUXCONFIG. If the TUXCONFIG is a UNIX
file, simply remove it. If it is stored on a raw disk, erase it by doing: echo
"" >$TUXCONFIG If the error persists, check for disk-type error
conditions that might cause problems writing to files. Finally, contact TUXEDO
System Technical Support, making sure to have the vtoc_errno that was
printed in the error message.
SEE ALSO
tmloadcf (1), ubbconfig (5)
293
ERROR: Failed to write the TUXCONFIG file (vtoc_errno=vtoc_errno).
DESCRIPTION
The
TUXCONFIG file is a binary file in the TUXEDO VTOC format. Each section of the
UBBCONFIG file (*RESOURCES, *MACHINES, etc.) is stored as a separate table in
the TUXCONFIG file. An error occurred while writing to a section of the
TUXCONFIG .
ACTION
If
the TUXCONFIG file is a UNIX file, the file system that it is in should be
checked to see if it has enough free space. The file should be checked to see
if its permissions allow writing. If the TUXCONFIG VTOC is being used to hold
only the TUXCONFIG tables (and not the TLOG or a TUXEDO/D database), then the
first thing to try is to recreate a new TUXCONFIG. If the TUXCONFIG file is a
UNIX file, simply remove it. If it is stored on a raw disk, erase it by doing:
echo "" >$TUXCONFIG
If
the error persists, check for disk-type error conditions that might cause
problems writing to files. Finally, contact TUXEDO System Technical Support,
making sure to have the vtoc_errno that was printed in the error
message.
LIBTUX
MESSAGES 300-399
300
ERROR: funcname: UNIX sys call error - errno_val
DESCRIPTION
An
attempt to access the VTOC through a system call such as open (2), lseek (2),
read (2), write (2), stat (2), or unlink (2) has failed because the system call
returned the errno indicated in the message.
ACTION
Contact
your TUXEDO System Technical Support.
301
ERROR: funcname: cannot free space
DESCRIPTION
An
attempt to free space that was allocated in the VTOC has failed because there
are no more available VTOC map entries.
ACTION
Contact
your TUXEDO System Technical Support.
302
ERROR: funcname: bad table name specified
DESCRIPTION
An
error occurred while either creating a new table entry or accessing an existing
table entry in the VTOC. If the error occurred while attempting to create a
table, either the table name already exists, or the name has a length of 0 or
is greater than the allowable table name size (GP_LOGICAL_NAME). If the error
occurred while attempting to access an existing table, either the name doesn't
exist, or the name has a length of 0 or is greater than the allowable table
name size.
ACTION
Contact
your TUXEDO System Technical Support.
303
ERROR: funcname: invalid arguments or request to function
DESCRIPTION
An
error occurred because the indicated function was invoked with invalid
arguments.
ACTION
Contact
your TUXEDO System Technical Support.
304
ERROR: funcname: bad device name or index specified
DESCRIPTION
An
attempt to access a device has failed because the name used was either of
length 0 or was longer than the allowable length of GP_LOGICAL_NAME .
ACTION
Contact
your TUXEDO System Technical Support.
305
ERROR: funcname: attempt to create overlapping devices
DESCRIPTION
An
error has occurred because of an overlap in devices. An overlap occurs if the
new device begins before the old device ends and the new device ends after the
old device begins.
ACTION
Contact
your TUXEDO System Technical Support.
306
ERROR: funcname: no entry remains to create device or table or open
table
DESCRIPTION
An
attempt to either create a device or table, or open a table has failed because
there are no more available slots in the device list.
ACTION
Contact
your TUXEDO System Technical Support.
308
ERROR: funcname: bad device type (not character special or regular)
DESCRIPTION
An
attempt to create a disk entry has failed because an invalid device type has
been specified. The only two available device types are character special and
regular.
ACTION
Contact
your TUXEDO System Technical Support.
309
ERROR: funcname: cannot obtain lock on VTOC
DESCRIPTION
An
error has occurred because within the function _gp_vtoc_lock(), an attempt to
obtain a lock on the VTOC has failed.
ACTION
Contact
your TUXEDO System Technical Support.
310
ERROR: errcode: unknown vtoc error code
DESCRIPTION
An
error has occurred during an access of the VTOC and has resulted in the
indicated unrecognizable error code being returned.
ACTION
Contact
your TUXEDO System Technical Support.
311
ERROR: Cannot locate free block in tlog
DESCRIPTION
An
attempt to locate and write to a free block in the transaction log has failed.
ACTION
Retry
the operation and if the problem persists, contact your TUXEDO System Technical
Support.
312
ERROR: Transaction log wrong page number
DESCRIPTION
An
attempt to access particular page of the transaction log has failed because the
referenced page is outside of the bounds of the transaction log.
ACTION
Retry
the operation and if the problem persists, contact your TUXEDO System Technical
Support.
313
ERROR: Log warmstart can only be called by BBL
DESCRIPTION
An
attempt to warmstart has failed because only the BBL is allowed to initiate
warmstarts.
ACTION
Contact
your TUXEDO System Technical Support.
314
INFO: Page page skipped, chksum didn't match
DESCRIPTION
The
indicated page was skipped while doing a warmstart because the checksum did not
match.
ACTION
No
action required.
315
ERROR: TLOG not in an understandable format. Different release
DESCRIPTION
The
format of the transaction log is unrecognizable. The release of the software is
different than the release of the transaction log.
ACTION
Contact
your TUXEDO System Technical Support.
316
ERROR: Transaction log file exists
DESCRIPTION
An
attempt to create the transaction log has failed because a transaction log
already exists.
ACTION
If
a transaction log exists, remove it and retry the desired operation. If the
problem persists, contact your TUXEDO System Technical Support.
317
ERROR: Log start can only be called by BBL or TMS
DESCRIPTION
A
call to internal function _tlog_start () has failed because the caller is
neither the BBL nor the TMS .
ACTION
Contact
your TUXEDO System Technical Support.
318
ERROR: Log start cannot get tlog information
DESCRIPTION
An
error occurred in attempting to open the transaction log. Either the *MACHINES
section of the configuration file could not be opened, or the current machine
id has not been defined in that configuration file.
ACTION
Check
and ensure the accuracy of the TUXCONFIG file, and if the problem persists,
contact your TUXEDO System Technical Support.
319
ERROR: Log start cannot open tlog
DESCRIPTION
An
error occurred attempting to open the transaction log with read and write
access.
ACTION
Check
and ensure that the appropriate permissions are set on the transaction log and
on the directory in which the transaction log resides. If the problem persists,
contact your TUXEDO System Technical Support.
320
ERROR: BB TLOGSIZE differs from number of pages in TLOG file
DESCRIPTION
An
error has occurred opening the transaction log because the actual size of the
TLOG differs from the size maintained by the BB .
ACTION
Retry
the desired operation, and if the problem persists, contact your TUXEDO System
Technical Support.
321
ERROR: Memory allocation failure
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using malloc
() has failed within tpacall ().
ACTION
Make
sure the operating system parameters are set correctly for the amount of memory
on the machine and the amount of memory that can be used by a process. Reduce
the memory usage on the machine or increase the amount of physical memory on
the machine.
SEE ALSO
tpcall(3)
322
ERROR: Message presend routine failed
DESCRIPTION
The
presend routine which performs some preliminary checking on the message before
it is encoded and sent has failed; therefore the message will not be sent.
ACTION
Make
sure the messages you are attempting to send have the length and pointer fields
set correctly. If the problem persists, contact your TUXEDO System Technical
Support.
323
ERROR: Invalid data length of 0, data not self describing
DESCRIPTION
An
attempt to send a message that has a data length of 0 has failed.
ACTION
Make
sure the messages you are attempting to send have the length and pointer fields
set correctly. If the problem persists, contact your TUXEDO System Technical
Support.
324
ERROR: Encoding of message header failed
DESCRIPTION
An
attempt to encode the header of the message has failed, therefore the message
has not been sent.
ACTION
Make
sure the messages you are attempting to send have the message header length and
pointer fields set correctly. If the problem persists, contact your TUXEDO
System Technical Support.
325
ERROR: Encoding of message data failed
DESCRIPTION
An
attempt to encode the data of the message has failed, therefore the message has
not been sent.
ACTION
Make
sure the messages you are attempting to send have the message data length and location
fields set correctly. If the problem persists, contact your TUXEDO System
Technical Support.
327
ERROR: Invalid table type desired
DESCRIPTION
An
internal function has failed because it attempted to access an invalid table.
ACTION
Contact
your TUXEDO System Technical Support.
328
ERROR: No space in Bulletin Board for tablename
DESCRIPTION
An
attempt to allocate a free entry in the Bulletin Board for tablename has
failed because it is full.
ACTION
Re-configure
the application to increase the size of the associated table.
329
ERROR: Tried to free non-alloced tmrte
DESCRIPTION
An
attempt to free a registry table entry has failed because the table entry has
not yet been allocated.
ACTION
Contact
your TUXEDO System Technical Support.
330
ERROR: Invalid table type given
DESCRIPTION
An
internal function has failed because it attempted to access an invalid table.
ACTION
Contact
your TUXEDO System Technical Support.
331
ERROR: No registry table entries
DESCRIPTION
There
are no more free entries in the registry table, so an attempt to allocate an
entry has failed.
ACTION
Contact
your TUXEDO System Technical Support.
332
ERROR: Memory allocation failure
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using malloc()
failed. This message is issued when a system process (for example, DBBL or BBL)
initializes and its call to malloc() fails.
ACTION
Make
sure the operating system parameters are set correctly for the amount of memory
on the machine and the amount of memory that can be used by a process. Reduce
the memory usage on the machine or increase the amount of physical memory on
the machine.
SEE ALSO
ulimit(2)
in UNIX system reference manuals
333
ERROR: No DBBL
DESCRIPTION
A
program was booted in an MP configuration without the Bulletin Board existing.
ACTION
Clean
up any IPC resources and re-boot the application from scratch.
SEE ALSO
tmboot(1)
334
ERROR: No BBL
DESCRIPTION
A
program was booted without the Bulletin Board existing.
ACTION
Clean
up any IPC resources and re-boot the application from scratch.
SEE ALSO
tmboot(1)
335
ERROR: Wrong bulletin board type or IPCKEY not unique
DESCRIPTION
Either
the bulletin board type has been changed for this application and the old
bulletin board (in shared memory) still exists, or the IPCKEY for the
application being booted is not unique (another application is using the same
IPCKEY and has attached to shared memory using that IPCKEY as the shared memory
id).
ACTION
Edit
the UBBCONFIG configuration file, change the IPCKEY to a unique value, reload
the TUXCONFIG using tmloadcf , and reboot the application.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
336
ERROR: semget err: errno=errno_val, key = key_val
DESCRIPTION
While
initializing the application, a system semaphore could not be created.
ACTION
Look
up the errno_val in errno.h to see its name. There are several possible
causes. ENOSPC indicates that not enough semaphores are configured in the
operating system; re-configure the OS to have more semaphore identifiers or
sets. EACCES indicates that the user executing the command does not have
permissions, which could be due to another application using the same ICPKEY.
Check the owner of the semaphore using the key_val and the ipcs(1)
command, and change IPCKEY if necessary.
337
ERROR: semctl err: errno=errno_val, key=key_val, id=id_val
DESCRIPTION
While
initializing the application, the status of a system semaphore could not be
obtained.
ACTION
Look
up the errno_val in errno.h to see its name. There are several possible
causes. EACCES indicates that the user executing the command does not have
permissions, which could be due to another application using the same ICPKEY.
Check the owner of the semaphore using the key_val and the ipcs(1)
command. EINVAL could indicate that the semaphore was destroyed during shutdown
of the system while another user tried to activate the system.
338
ERROR: BB semaphore not initialized within 10 seconds (key=0xkey_val).
DESCRIPTION
While
initializing the application, a program found the TUXEDO system semaphore
existed but was not initialized within 10 seconds.
ACTION
Use
the ipcs(1) command to check the specified key value, checking the creator
process to see if it is alive. Remove the IPC resources and re-boot the
application.
339
ERROR: Creating process may be dead; manual intervention required.
DESCRIPTION
While
initializing the application, a program found the TUXEDO system semaphore
existed but was not initialized within 10 seconds. This is related to message
338.
ACTION
Use
the ipcs(1) command to check the specified key value, checking the creator
process to see if it is alive. Remove the IPC resources and re-boot the
application.
340
ERROR: Wrong configuration file
DESCRIPTION
Either
the configuration parameters have been changed for this application and the old
bulletin board (in shared memory) still exists, or the IPCKEY for the
application being booted is not unique (another application is using the same
IPCKEY and has attached to shared memory using that IPCKEY as the shared memory
id).
ACTION
Edit
the UBBCONFIG configuration file, change the IPCKEY to a unique value, reload
the TUXCONFIG using tmloadcf , and reboot the application.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
341
ERROR: Could not allocate bulletin board shared memory
DESCRIPTION
While
initializing the TUXEDO application, shared memory could not be allocated for
the Bulletin Board.
ACTION
Check
that the IPCKEY in the UBBCONFIG configuration file is not being used by
another application for shared memory. Check that enough shared memory has been
configured.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
342
ERROR: Could not allocate bulletin board shared memory
DESCRIPTION
While
initializing the TUXEDO application, shared memory could not be allocated for
the Bulletin Board.
ACTION
Check
that the IPCKEY in the UBBCONFIG configuration file is not being used by
another application for shared memory. Check that enough shared memory has been
configured.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
343
ERROR: Could not find DBBL
DESCRIPTION
While
initializing the TUXEDO application, shared memory could not be allocated for
the Bulletin Board.
ACTION
The
application is configured as mode MP and the DBBL has not created the BB. Make
sure that the DBBL is booted first and did not die. Check that the IPCKEY in
the UBBCONFIG configuration file is not being used by another application for
shared memory. Check that enough shared memory has been configured.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
344
ERROR: Could not allocate bulletin board shared memory
DESCRIPTION
While
initializing the TUXEDO application, shared memory could not be allocated for
the Bulletin Board.
ACTION
Check
that the IPCKEY in the UBBCONFIG configuration file is not being used by
another application for shared memory. Check that enough shared memory has been
configured.
SEE ALSO
tmloadcf
(1), ubbconfig (5)
345
ERROR: Cannot find DBBL
DESCRIPTION
An
attempt was made to send a message to the DBBL and its whereabouts could not be
ascertained either from the BB or from a BRIDGE process.
ACTION
Check
for a partitioned network, corrupted shared memory, or if all administrative
processes are running.
346
ERROR: Not a Bulletin Board
DESCRIPTION
The
TUXEDO System application's IPCKEY is clashing with another application's use
of UNIX IPC resources, specifically with a UNIX IPC semaphore.
ACTION
Choose
another IPCKEY for your TUXEDO System application.
SEE ALSO
tmadmin(1)
347
ERROR: Bulletin Board version mismatch
DESCRIPTION
The
process trying to attach to the Bulletin Board differs in release from the
Bulletin Board creator. The process fails to join the application.
ACTION
Make
sure that $TUXDIR/bin points to the most current release of the TUXEDO System.
Also, make sure application processes have been re-linked or re-compiled with
the latest release.
349
ERROR: Memory allocation failure
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using malloc()
failed. This message is issued when a system process (for example, DBBL or BBL)
initializes and its call to malloc() fails.
ACTION
Make
sure the operating system parameters are set correctly for the amount of memory
on the machine and the amount of memory that can be used by a process. Reduce
the memory usage on the machine or increase the amount of physical memory on
the machine.
SEE ALSO
ulimit(2)
in UNIX system reference manuals
350
ERROR: Configuration file parameters do not match existing bulletin board.
DESCRIPTION
When
a process initially tries to join the application, this message is issued when
the process' configuration file parameters do not match the existing bulletin
board. This could happen, for example, if the application's ubbconfig file is
modified and re-loaded with tmloadcf.
ACTION
Make
sure that your TUXCONFIG file matches that with which the system was
initialized.
SEE ALSO
tmloadcf(1)
351
ERROR: Error building node tables
DESCRIPTION
When
a BBL initializes, it populates certain areas of the bulletin board. This
message is issued when a BBL encounters an error creating the node table in the
bulletin board. The node table contains entries for the machines in the
*MACHINES section of the ubbconfig file. This error occurs when a node is
running with a pre-4.2.1 release of the TUXEDO System. Releases before 4.2.1
supported at most 50 nodes in an application.
ACTION
If
your application contains more than 50 nodes specified in your ubbconfig file,
then all nodes in the application must be release 4.2.1 or higher.
SEE ALSO
ubbconfig(5)
352
ERROR: Error resetting ULOGPFX
DESCRIPTION
The
program failed to set the prefix for the userlog file either because dynamic
space allocation failed or because the TUXCONFIG file was corrupted. The
userlog prefix will be $APPDIR/ULOG .
ACTION
If
other messages in the userlog indicate that the TUXCONFIG file is corrupted,
you should re-load the TUXCONFIG file at your earliest convenience. If other
messages in the userlog indicate that your system is out of memory, then 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.
SEE ALSO
ubbconfig(5),
ulimit(2) in UNIX system reference manuals
353
ERROR: Error putting ENVFILE file into environment
DESCRIPTION
This
message is issued when an error occurs putting the process' ENVFILE into its
environment.
ACTION
See
the userlog for other messages that explain exactly which error occurred as
part of processing the process' ENVFILE .
SEE ALSO
ubbconfig(5)
354
WARN: Error changing directory to appdir (path) for LMID (lmid)
DESCRIPTION
When
this message is issued, an invalid APPDIR pathname is specified in the
*MACHINES section for the LMID shown in the message. The processes associated
with this LMID will use the default APPDIR for this TUXCONFIG.
ACTION
At
your earliest convenience, you should set APPDIR to a valid pathname and
re-load your TUXCONFIG with tmloadcf.
SEE ALSO
tmloadcf(1),
ubbconfig(5)
355
ERROR: No BBL on this machine
DESCRIPTION
The
process that issued this message tried to join a site that was in the midst of
being shut down.
ACTION
No
action required.
356
ERROR: Reached UNIX limit on semaphore ids
DESCRIPTION
The
BBL could not create any more semaphore ids because the UNIX system-imposed
limit on the maximum number of allowed semaphores system-wide would be exceeded.
ACTION
Contact
your TUXEDO System Technical Support about resetting the number of UNIX
semaphores as per the IPC tuning guidelines in the "TUXEDO Installation
Guide" .
SEE ALSO
"TUXEDO
Installation Guide"
357
ERROR: Cannot create enough semaphores for BB, (UNIX limit), MAXACCESSERS too
high
DESCRIPTION
When
a BBL initializes, it creates one or more sets of semaphores for serializing
access to the bulletin board. The number of semaphores created per machine is
roughly equal to the value of MAXACCESSERS on that machine. This message is
printed when the BBL cannot create as many semaphores as it needs.
ACTION
If
possible, decrease the value of MAXACCESSERS for the machine. If several
machines are used in your application, it is advisable to specify for each
*MACHINES section entry a MAXACCESSERS value that is roughly the number of
System/T client and server processes that will run simultaneously on that
machine.
SEE ALSO
ubbconfig(5)
358
ERROR: Reached UNIX limit on semaphore ids
DESCRIPTION
The
BBL could not create any more semaphore ids because the UNIX system-imposed
limit on the maximum number of allowed semaphores system-wide would be
exceeded.
ACTION
Contact
your TUXEDO System Technical Support about resetting the number of UNIX system
semaphores as per the IPC tuning guidelines in the "TUXEDO Installation
Guide" .
SEE ALSO
"TUXEDO
Installation Guide"
359
ERROR: Cannot create enough semaphores for BB, (UNIX limit), MAXACCESSERS too
high
DESCRIPTION
When
a BBL initializes, it creates one or more sets of semaphores for serializing
access to the bulletin board. The number of semaphores created per machine is
roughly equal to the value of MAXACCESSERS on that machine. This message is
printed when the BBL cannot create as many semaphores as it needs.
ACTION
If
possible, decrease the value of MAXACCESSERS for the machine. If several
machines are used in your application, it is advisable to specify for each
*MACHINES section entry a MAXACCESSERS value that is roughly the number of
System/T client and server processes that will run simultaneously on that
machine.
SEE ALSO
ubbconfig(5)
360
ERROR: semctl for initializing sems failed: errno
DESCRIPTION
Once
the BBL creates a semaphore set used for serializing access to the BB , it
initializes it. This message is issued when the BBL fails to initialize a
semaphore set as locked. The issued message contains the UNIX system error
number, errno, which can be used to determine the exact nature of the
error.
ACTION
Contact
your TUXEDO System Technical Support.
SEE ALSO
semctl(2)
in UNIX system reference manuals
361
ERROR: semctl for initializing sems failed: errno
DESCRIPTION
Once
the BBL creates a semaphore set used for serializing access to the BB , it
initializes it. This message is issued when the BBL fails to initialize a
semaphore set with the administrator's UNIX uid , gid , and permissions as
specified in the ubbconfig file. The issued message contains the UNIX system
error number, errno, which can be used to determine the exact nature of
the error.
ACTION
Contact
your TUXEDO System Technical Support.
SEE ALSO
semctl(2)
in UNIX system reference manuals
362
ERROR: TPEOS time set errno errno
DESCRIPTION
As
part of initializing the global transaction table, the BBL calls the time()
system call. This message is issued when the call to time() fails. The message
includes the error number, errno, which can be used to determine the
exact nature of the error.
ACTION
Consult
the time(2) manual page to determine the exact nature of the error.
SEE ALSO
time(2) in UNIX system reference
manuals
364
ERROR: Failure during send/receive of remote procedure call
DESCRIPTION
An
internal error occurred while attempting to send a remote procedure call.
ACTION
Check
that the DBBL is running, and retry the desired operation. If the error occurs
again, contact your TUXEDO System Technical Support.
370
ERROR: Error setting time for transaction counter, errno errno
DESCRIPTION
As
part of starting a new transaction, the time() system call is issued. This
message is issued when the call to time() fails. The message includes the error
number, errno, which can be used to determine the exact nature of the
error.
ACTION
Consult
the time(2) manual page to determine the exact nature of the error.
SEE ALSO
time(2)
in UNIX system reference manuals
376
ERROR: tpabort: xa_rollback returned status
DESCRIPTION
This
message is issued if the process aborting a transaction encounters an error
upon calling the database resource manager with xa_rollback(). The message
prints the error code that the function returned.
ACTION
Contact
your TUXEDO System Technical Support or your database system vendor. See the
userlog for more information on the outcome of the transaction. Also, use
tmadmin's printtrans command to find out more information about the
transaction.
SEE ALSO
tmadmin(1)
377
ERROR: tpabort state state
DESCRIPTION
This
message is issued when a transaction is being aborted and the state of the
transaction is such that the normal procedure for aborting the transaction
could not be followed. The state of the transaction is printed as part of this
message. If the state is TMGABORTED , then the transaction has already been
aborted; all other states reflect the various stages of two-phase commitment
(including heuristic outcomes).
ACTION
See
the userlog for more information about this transaction's completion. Also, use
tmadmin's printtrans command to find out more information about the
transaction.
SEE ALSO
tmadmin(1)
378
ERROR: Failed to determine uname
DESCRIPTION
An
attempt to determine the machine id through a call to uname (2) has failed.
ACTION
Make
sure the machine's uname is correctly configured. Retry the desired operation;
if the error occurs again, contact your TUXEDO System Technical Support.
381
ERROR: Cannot call ATMI routines until you have joined system
DESCRIPTION
This
message is issued if tpforward() is called outside of a service routine (for
example, by a client).
ACTION
Change
your application code to not use tpforward() in clients or outside of service
routines.
SEE ALSO
tpforward(3)
382
ERROR: Performed tpforward() with outstanding replies
DESCRIPTION
This
message is issued when a service routine calls tpforward() with outstanding
replies. The client that invoked this service routine receives an error,
TPESVCERR , from either tpcall() or tpgetrply(), if it was expecting a reply.
The service named by tpforward() is not invoked.
ACTION
You
should alter your service routine to call either tpgetrply() or tpcancel() for
all outstanding replies before calling tpforward(). If your service routine
encounters an application error and you need to return from the service
immediately, then use tpreturn() with TPFAIL .
SEE ALSO
tpcancel(3),
tpgetrply(3), tpforward(3), tpreturn(3)
389
WARN: Failed to set priority for TMS request
DESCRIPTION
When
a request is sent to the TMS to complete a transaction, the priority of the
request is set to optimize performance. This message is issued as a warning
when the system fails to override the default priority. The request is sent at
the default priority.
ACTION
No
action required.
390
ERROR: tpcommit msg failure, check GTT
DESCRIPTION
This
message is issued when the system encounters an error trying to receive the
reply to a request sent to a TMS to complete a transaction. This message is
typically issued when a system-level failure occurs.
ACTION
See
the userlog for more information about this transaction's completion and about
any communication error that may have occurred. Also, use tmadmin's printtrans
command to find out more information about the transaction and use the printnet
command to see the status of all machine connections in the network. This
command will report any network partitions.
SEE ALSO
tmadmin(1)
391
ERROR: No room to add group name
DESCRIPTION
This
message is issued when a transaction has visited more than 16 TUXEDO System
groups (as defined in the *GROUPS section of the ubbconfig file). At that
point, the transaction will not continue to propagate nor will it complete
successfully.
ACTION
Consider
combining groups or using data dependent routing to consolidate requests to
servers within the same group in order to allow your transaction to stay within
the 16 group maximum.
SEE ALSO
ubbconfig(5)
392
INFO: GTTELOG: GTRID: machine(machine) counter_time(0xtime)
counter(0xcount)
DESCRIPTION
This
message prints out the contents of a global transaction table entry. This
includes the transaction identifier (GTRID) , the transaction's state, and
other pertinent information that can be used by support personnel to help
locate problems with global transactions.
ACTION
No
action required.
SEE ALSO
See
Messages No. 393, 394, 395, and 396 in this chapter, and Message No. 408 in the
chapter on CMDTUX messages.
393
INFO: coordinator(group) group_count(count) tran_state(state)
DESCRIPTION
This
message is a continuation of message 392 in this chapter.
ACTION
No
action required.
SEE ALSO
See
Messages No. 392, 394, 395, and 396 in this chapter, and Message No. 408 in the
chapter on CMDTUX messages.
394
INFO: cmchid(val) q(val2) type(val3) iter(val4)
reg_index(val5)
DESCRIPTION
This
message is a continuation of message 392 in this chapter.
ACTION
No
action required.
SEE ALSO
See
Messages No. 392, 393, 395, and 396 in this chapter, and Message No. 408 in the
chapter on CMDTUX messages.
395
INFO: log_page(val) version(val2) tranflags(val3)
DESCRIPTION
This
message is a continuation of message 392 in this chapter.
ACTION
No
action required.
SEE ALSO
See
Messages No. 392, 393, 394, and 396 in this chapter, and Message No. 408 in the
chapter on CMDTUX messages.
396
INFO: GR[val]:name(val1)local(val2)state(val3)
DESCRIPTION
This
message is a continuation of message 392 in this chapter.
ACTION
No
action required.
SEE ALSO
See
Messages No. 392, 393, 394, and 395 in this chapter, and Message No. 408 in the
chapter on CMDTUX messages.
397
ERROR: Cannot allocate entry on GTT
DESCRIPTION
This
message is issued when no more room exists in the bulletin board to accommodate
transactions. This message can occur for a new transaction, in which case the
transaction will fail to begin. Or, this message can occur when an existing
transaction tries to instantiate itself on a server's bulletin board, in which
case the transaction will fail to commit. This message might reflect a
transient condition based on a large, "bursty" transaction volume.
ACTION
Consider
increasing the MAXGTT entry in your application's ubbconfig file if this
message occurs often or if too many transactions fail due to the current MAXGTT
setting. If you are already using the maximum value, and if you are also using
either the LOGGED value for the CMTRET keyword in the ubbconfig file or the
TP_CMT_LOGGED setting for tpscmt(3), then use the COMPLETE or TP_CMT_COMPLETE
settings, respectively, so that new transactions will not start until current
ones complete.
SEE ALSO
tpscmt(3),
tx_set_commit_return(3), ubbconfig(5)
398
ERROR: Cannot allocate entry on GTT, TMID creation failed
DESCRIPTION
This
message is issued when no more room exists in the bulletin board to accommodate
transactions. This message can occur for a new transaction, in which case the
transaction will fail to begin. Or, this message can occur when an existing
transaction tries to instantiate itself on a server's bulletin board, in which
case the transaction will fail to commit. This message might reflect a
transient condition based on a large, "bursty" transaction volume.
ACTION
Consider
increasing the MAXGTT entry in your application's ubbconfig file if this
message occurs often or if too many transactions fail due to the current MAXGTT
setting. If you are already using the maximum value, and if you are also using
either the LOGGED value for the CMTRET keyword in the ubbconfig file or the
TP_CMT_LOGGED setting for tpscmt(3), then use the COMPLETE or TP_CMT_COMPLETE
settings, respectively, so that new transactions will not start until current
ones complete.
SEE ALSO
tpscmt(3),
tx_set_commit_return(3), ubbconfig(5)
399
ERROR: xa_forget returned status
DESCRIPTION
When
a database resource manager (RM) makes a unilateral decision to complete a
global transaction and its decision is in conflict with the TUXEDO System's
decision, this situation is known as a "heuristic decision". The RM
is required to log on stable storage this decision until the TUXEDO System
explicitly tells the RM to forget its decision. This error message is issued
when the RM encounters an error while processing the "forget"
request.
ACTION
Contact
your TUXEDO System Technical Support or your database system vendor.
CMDTUX
MESSAGES 400-499
401
ERROR: service request service_name handled by DBBL failed, msg
DESCRIPTION
An
administrative service request handled by the DBBL failed with a non-fatal
error. These requests include tmadmin requests, tmboot and tmshutdown requests.
ACTION
The
service requests failed with tperrno and Uunixerr , if any. Take proper action
according to the tperrno and/or Uunixerr , or contact your TUXEDO System
Technical Support.
SEE ALSO
tmadmin
(1), tmboot (1), tmshutdown (1)
402
INFO: The temporary DBBL is exiting system
DESCRIPTION
A
temporary DBBL was brought up to clean up the partitioned BBLs. This temporary
DBBL is currently exiting the system.
ACTION
No
action required.
SEE ALSO
tmshutdown
(1)
403
INFO: The DBBL is exiting system
DESCRIPTION
The
DBBL is currently exiting the system. All other processes have been shut down
already.
ACTION
No
action required.
SEE ALSO
tmshutdown
(1)
404
WARN: Memory allocation failure
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using malloc
() failed while the DBBL was checking the status of all BBLs, marking unreachable
BBLs and then cleaning up.
ACTION
Make
sure the operating system parameters are set correctly for the amount of memory
on the machine and the amount of memory that can be used by a process. Reduce
the memory usage on the machine or increase the amount of physical memory on
the machine.
406
WARN: SIGTERM was ignored while shutting down the DBBL
DESCRIPTION
SIGTERM
was received and ignored while shutting down the DBBL .
ACTION
See
tmshutdown command for shutdown procedures.
SEE ALSO
tmshutdown
(1)
407
ERROR: Unable to add group group_name to TMGCTL table - no space
DESCRIPTION
System/T
attempted to add the specified group in the transaction management data table,
but the space allocated for the number of groups was exceeded.
ACTION
Please
modify your configuration and increase the number of server groups that are to
be used. Then reload the TUXCONFIG file and reboot your application. If you
need more than the allowable maximum number of server groups, contact your
TUXEDO System Technical Support.
SEE ALSO
"TUXEDO
Administrator's Guide" tmloadcf (1), tmboot (1), ubbconfig (5)
408
ERROR: Unable to add group group_name to TMGTT table - no space
DESCRIPTION
System/T
was in the process of recovering transactions while performing a tpsvrinit ().
System/T attempted to add the specified group to the global transaction table,
but the space allocated for the number of groups was exceeded.
ACTION
Contact
your TUXEDO System Technical Support.
409
ERROR: xa_recover() returned count for group groupname
DESCRIPTION
System/T
was in the process of recovering transactions while performing a tpsvrinit ().
The resource manager returned an error when xa_recover () was called to find
pre-committed global transactions.
ACTION
Check
the error mechanism for the associated resource manager to find the nature of
the error.
410
WARN: tpsvrinit() changing state of group groupname from TMGHCOMMIT to
TMGABORTED
DESCRIPTION
System/T
was in the process of recovering transactions while performing a tpsvrinit ().
While the transaction coordinator was restarting, messages about groups may
have been lost; as such the coordinator may have an incomplete list of groups
unless the transaction was logged. Since this is a case of the coordinator restarting,
the transaction must not have been logged, so the particular transaction must
be aborted.
ACTION
Please
repeat the transaction.
411
ERROR: tpsvrinit() found transaction state state_val
DESCRIPTION
System/T
was in the process of recovering transactions while performing a tpsvrinit ().
The transaction state was not one of the valid states.
ACTION
Contact
your TUXEDO System Technical Support.
412
ERROR: tpsvrinit() unable to locate entry for TMS in the Bulletin Board
DESCRIPTION
System/T
was in the process of recovering transactions while performing a tpsvrinit ().
The function was unable to locate an entry for the first TMS in a group in the
Bulletin Board.
ACTION
Contact
your TUXEDO System Technical Support.
413
ERROR: tpsvrinit() unable to update entry for TMS in the Bulletin Board
DESCRIPTION
System/T
was in the process of recovering transactions while performing a tpsvrinit ().
The function was unable to update an entry for the first TMS in a group in the
Bulletin Board.
ACTION
Contact
your TUXEDO System Technical Support.
414
ERROR: TMS() got request for invalid Global Transaction ID
DESCRIPTION
System/T
server TMS was given an invalid global transaction identifier, and therefore
could not complete the necessary operation.
ACTION
Contact
your TUXEDO System Technical Support.
415
ERROR: Invalid service identifier requested while processing transactions
DESCRIPTION
An
invalid service identifier identifier was specified for processing, and
therefore could not complete the necessary operation.
ACTION
Contact
your TUXEDO System Technical Support.
416
ERROR: service svcname sent to non-coordinator
DESCRIPTION
The
TMS was unable to execute the service svcname because the service was
sent to a non-coordinator for the transaction.
ACTION
Contact
your TUXEDO System Technical Support.
417
ERROR: TMS_MANAGE found transaction state stateval
DESCRIPTION
While
processing transactions, an invalid state was reached.
ACTION
Contact
your TUXEDO System Technical Support.
418
ERROR: Unable to add message groups to transaction
DESCRIPTION
While
processing transactions, the System/T attempted to add message groups to the
transaction. The operation was unsuccessful.
ACTION
Contact
your TUXEDO System Technical Support.
419
WARN: Commit found no participants
DESCRIPTION
While
processing a commit request, the TMS found no participants. The transaction
will be deleted.
ACTION
No
action required.
420
WARN: Commit coordinator gone
DESCRIPTION
System/T
was processing transactions. In a transaction, the first Resource Manager group
is the transaction coordinator, so it must be the first at its site. However,
it is possible that the site went down and came back up before the arrival of a
TMS_MANAGE message.
ACTION
Contact
your TUXEDO System Technical Support.
421
ERROR: Invalid transaction state state
DESCRIPTION
System/T
was committing a transaction. During a one-phase commit step, the transaction
state was invalid.
ACTION
Contact
your TUXEDO System Technical Support.
422
ERROR: XA_RETRY not supported for one-phase commit
DESCRIPTION
System/T
was committing a transaction. During a one-phase commit, the XA return code was
XA_RETRY , which is not supported for one-phase commit.
ACTION
Check
the error reporting mechanism for the associated resource manager.
423
WARN: One-phase commit - xa_commit returned error_val
DESCRIPTION
System/T
was committing a transaction. During a one-phase commit, the XA return code was
not XA_OK , XA_HEURCOM , XA_RETRY , XAER_RMFAIL , XA_HEURHAZ , XA_HEURRB ,
XA_HEURMIX , or XAER_RMERR .
ACTION
Check
the error reporting mechanism for the associated resource manager.
424
ERROR: Commit found invalid state - group group state state
DESCRIPTION
System/T
was committing a transaction. During a one-phase commit, the XA return code was
not XA_OK , XA_HEURCOM , XA_RETRY , XAER_RMFAIL , XA_HEURHAZ , XA_HEURRB ,
XA_HEURMIX , or XAER_RMERR .
ACTION
Contact
your TUXEDO System Technical Support.
425
ERROR: Precommit found an invalid transaction state state
DESCRIPTION
System/T
was precommitting a transaction. The transaction state was not one of the
states expected.
ACTION
Contact
your TUXEDO System Technical Support.
426
ERROR: Precommit found invalid state group group state state
DESCRIPTION
System/T
was precommitting a transaction. The transaction state for the indicated group
was not as expected.
ACTION
Contact
your TUXEDO System Technical Support.
427
ERROR: Precommit transaction state state after xa_precom failure
DESCRIPTION
System/T
was precommitting a transaction. The transaction state after xa_precom
failure was not as expected.
ACTION
Contact
your TUXEDO System Technical Support.
428
ERROR: Precommit transaction state state after xa_precom
DESCRIPTION
System/T
was precommitting a transaction. The transaction state after xa_precom
was not as expected.
ACTION
Contact
your TUXEDO System Technical Support.
429
ERROR: Rollback found invalid transaction state state
DESCRIPTION
System/T
was rolling back a transaction. The transaction state was not as expected.
ACTION
Contact
your TUXEDO System Technical Support.
430
ERROR: Completion found invalid transaction state state
DESCRIPTION
System/T
was completing a transaction. The transaction state was not as expected.
ACTION
Contact
your TUXEDO System Technical Support.
431
ERROR: Received a rollback request for a decided transaction
DESCRIPTION
System/T
received a rollback request for a decided transaction.
ACTION
Contact
your TUXEDO System Technical Support.
432
ERROR: Group group at coordinator site received rollback request in
ready state
DESCRIPTION
System/T
received a request to rollback a transaction that is already in
"ready" state.
ACTION
Contact
your TUXEDO System Technical Support.
433
ERROR: Rollback - xa_abort returned error for group group
DESCRIPTION
System/T
was rolling back a transaction. The resource manager returned an error when
xa_abort was called. The XA return code was not XA_OK , XA_HEURRB , or
XAER_NOTA .
ACTION
Check
the error reporting mechanism for the associated resource manager.
434
WARN: Rollback changing group group from heuristic commit to rolled back
DESCRIPTION
System/T
was rolling back a transaction. The transaction state of the group was changed
from heuristic commit to rolled back.
ACTION
No
action required.
435
ERROR: Rollback found invalid state - group group in state state
DESCRIPTION
System/T
was rolling back a transaction. The transaction state of the group was not one
of the expected states.
ACTION
Contact
your TUXEDO System Technical Support.
436
WARN: Heuristic rollback of transaction
DESCRIPTION
System/T
received a request to heuristically rollback a global transaction. This request
was generated via tmadmin aborttrans .
ACTION
No
action required.
437
WARN: Heuristic rollback of transaction
DESCRIPTION
System/T
received a request to heuristically rollback a transaction for this group only.
This request was generated via tmadmin aborttrans .
ACTION
No
action required.
438
WARN: Heuristic rollback not allowed for decided transaction
DESCRIPTION
A
request was received to heuristically rollback a transaction that is already in
decided state. This request was generated via tmadmin aborttrans .
ACTION
No
action required.
439
WARN: Heuristic rollback not allowed for ready transaction at coordinator site
DESCRIPTION
System/T
received a request to heuristically rollback a transaction that is in ready
state. The request was generated by the tmadmin aborttrans command.
ACTION
The
request will be ignored. No action required.
440
WARN: Transaction heuristically rolled back for group groupname
DESCRIPTION
System/T
heuristically rolled back a transaction based on a request from the tmadmin
aborttrans command.
ACTION
No
action required.
441
ERROR: Rollback xa_abort returned error
DESCRIPTION
System/T
was rolling back a transaction. The xa_rollback() function returned an
error that was not one of the expected values.
ACTION
Check
the error reporting mechanism for the associated resource manager.
442
ERROR: Timeout found invalid state state
DESCRIPTION
System/T
was processing a timeout request for a transaction and found an unexpected
state, state.
ACTION
Contact
your TUXEDO System Technical Support.
443
ERROR: tms_timeout group group xa_abort returned error
DESCRIPTION
System/T
was processing a timeout request for a transaction. The resource manager
returned an error from xa_abort .
ACTION
Check
the error reporting mechanism for the associated resource manager.
444
WARN: Heuristic commit for group group
DESCRIPTION
This
informative message indicates that the transaction has been heuristically
committed as a result of a tmadmin committrans command.
ACTION
No
action required.
445
ERROR: Heuristic commit xa_commit for group group returned error
DESCRIPTION
While
heuristically committing a transaction, the resource manager returned an error
condition from xa_commit().
ACTION
Check
the error reporting mechanism for the associated resource manager.
446
ERROR: Commit found transaction state state
DESCRIPTION
While
committing a transaction, an unexpected transaction state was found.
ACTION
Contact
your TUXEDO System Technical Support.
447
ERROR: xa_commit returned error for group group
DESCRIPTION
While
committing a transaction, the resource manager returned an error from xa_commit
.
ACTION
Check
the error reporting mechanism for the associated resource manager.
448
ERROR: Commit found invalid state for group group state state
DESCRIPTION
While
committing a transaction, an invalid state was found for the specified group.
ACTION
Contact
your TUXEDO System Technical Support.
449
ERROR: Ready indication for missing group group
DESCRIPTION
While
committing a transaction, a ready indication was received for a group that is
not part of the transaction. The indication will be ignored.
ACTION
Contact
your TUXEDO System Technical Support.
450
ERROR: Ready found invalid state for group group state state
DESCRIPTION
While
committing a transaction, a ready indication was received for a group that is
in an invalid state. The indication will be ignored.
ACTION
Contact
your TUXEDO System Technical Support.
451
ERROR: Reday indication found transaction state state
DESCRIPTION
While
committing a transaction, a ready indication was received for a transaction
that is in an unexpected state.
ACTION
Contact
your TUXEDO System Technical Support.
452
ERROR: Status request transaction state state group group state state
DESCRIPTION
While
processing a status request for a transaction, unexpected states were found for
the transaction and the specified group.
ACTION
Contact
your TUXEDO System Technical Support.
453
ERROR: Transaction log commit failed
DESCRIPTION
While
committing a transaction, updating the transaction log failed.
ACTION
Check
the userlog for earlier messages indicating the nature of the failure.
454
ERROR: Status request found transaction state state
DESCRIPTION
While
processing a status request, an invalid transaction state was found.
ACTION
Contact
your TUXEDO System Technical Support.
455
ERROR: tpsvrdone can't find group group
DESCRIPTION
The
TMS was being shut down. A group entry was to be cleaned up, but no information
on that group was found.
ACTION
Contact
your TUXEDO System Technical Support.
456
ERROR: tpsvrdone can't get queue entry
DESCRIPTION
The
TMS was being shut down. A group entry was to be cleaned up, but System/T was
unable to get information on the Queue Table.
ACTION
Contact
your TUXEDO System Technical Support.
457
INFO: TMS tpsvrdone complete
DESCRIPTION
The
TMS shutdown was completed safely.
ACTION
No
action required.
458
ERROR: Memory allocation failure
DESCRIPTION
The
distinguished TMS was about to be shut down. However, System/T was unable to
allocate required memory. The memory allocated was to have been used to step
through server information on all the TMS s to ensure that the distinguished
TMS could shut down properly. In this case, since memory could not be
allocated, it is not possible to determine the state of each TMS , so System/T
allows the shutdown to proceed anyway.
ACTION
Make
sure the operating system parameters are set correctly for the amount of memory
on the machine and the amount of memory that can be used by a process. Reduce
the memory usage on the machine or increase the amount of physical memory on
the machine.
459
ERROR: Invalid sendlist error
DESCRIPTION
The
TMS encountered an error while trying to send a message. This condition should
never arise.
ACTION
Contact
your TUXEDO System Technical Support.
460
ERROR: TMS send - failed to set priority for TMS request
DESCRIPTION
The
TMS was managing a transaction and had attempted to set the priority of a TMS
request, and that function failed.
ACTION
Contact
your TUXEDO System Technical Support.
461
ERROR: tms_send tpacall service code
DESCRIPTION
The
TMS was managing a transaction and had attempted to send a message to a TMS
service via a tpacall (), and that call failed. The numeric value displayed in
the message identifies the service that was used.
ACTION
A
possible cause for this error may be that the TMS process has terminated for
some reason. Please check and ensure that all TMS processes are running. If
further assistance is needed, please contact the System/T Administrator.
462
WARN: Can't send reply to committer
DESCRIPTION
The
TMS was managing a transaction and had attempted to send a reply to the
committer of the transaction. The call failed.
ACTION
Please
examine the userlog for additional messages included prior to this one. If
further assistance is needed, contact your TUXEDO System Technical Support.
463
ERROR: could not contact BBL to abort old transactions
DESCRIPTION
The
TMS was in the process of aborting old transactions and was unable to contact
the BBL process to get information about the transactions.
ACTION
Contact
your TUXEDO System Technical Support.
464
ERROR: could not contact DBBL to abort old transactions
DESCRIPTION
The
TMS was in the process of aborting old transactions and was unable to contact
the DBBL process to get information about the transactions.
ACTION
Please
ensure that the DBBL process is running. Contact your TUXEDO System Technical
Support.
465
ERROR: Failed to abort old transactions
DESCRIPTION
The
TMS was in the process of aborting old transactions and was unable to do so. An
underlying system call had failed, in all probability a request/response call
to the BRIDGE process.
ACTION
Contact
your TUXEDO System Technical Support.
468
ERROR: Memory allocation failure
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using malloc
() failed while allocating a message. The TUXEDO System/T boot process for
non-master nodes involves running a bootstrap-Bridge process, called the
BSBRIDGE . The BSBRIDGE starts the BBL on that node, and the BBL starts the
real BRIDGE , which then shuts down the BSBRIDGE . The BRIDGE does this by
sending a message to the BSBRIDGE . The code that allocated the space for that
message failed.
ACTION
Make
sure the operating system parameters are set correctly for the amount of memory
on the machine and the amount of memory that can be used by a process. Reduce
the memory usage on the machine or increase the amount of physical memory on
the machine.
469
ERROR: Can't send shutdown message to the BSBRIDGE
DESCRIPTION
Please
refer to the description for Message 468 above. The send of the shutdown
message to the BSBRIDGE failed. This could be caused by full message queues on
the system.
ACTION
Contact
your TUXEDO System Technical Support.
470
WARN: Memory allocation failure
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using malloc
() failed while the BRIDGE process was creating an internal buffer for an
identification message. Failure to send this message will not prevent the
BRIDGE process from running. However, the network connection being established
cannot be used bi-directionally, so some system resources will be wasted.
ACTION
Make
sure the operating system parameters are set correctly for the amount of memory
on the machine and the amount of memory that can be used by a process. Reduce
the memory usage on the machine or increase the amount of physical memory on
the machine.
471
WARN: Error sending message OB_IDENT process
DESCRIPTION
The
BRIDGE process could not send an OB_IDENT identification message over a newly
created connection. This failure will not prevent the BRIDGE process from
running. However, the network connection being established cannot be used
bi-directionally, so some system resources will be wasted.
ACTION
It
is likely that further errors will occur over this connection. Try to
reestablish the link using tmadmin 's reconnect command. If this fails, shut
down and reboot the TUXEDO System on this machine.
473
ERROR: Could not find DBBL
DESCRIPTION
The
BSBRIDGE (bootstrap bridge) process could not contact the DBBL on the master or
backup machine during its initialization.
ACTION
Check
the master machine's network addresses in the *NETWORK section of the
configuration file. Check for and resolve any networking problems.
476
ERROR: Memory allocation failure
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using malloc
() failed while attempting to contact the DBBL .
ACTION
Make
sure the operating system parameters are set correctly for the amount of memory
on the machine and the amount of memory that can be used by a process. Reduce
the memory usage on the machine or increase the amount of physical memory on
the machine.
480
ERROR: Memory allocation failure
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using malloc
() failed while trying to allocate a buffer for receiving a message in the
BRIDGE .
ACTION
Make
sure the operating system parameters are set correctly for the amount of memory
on the machine and the amount of memory that can be used by a process. Reduce
the memory usage on the machine or increase the amount of physical memory on
the machine.
SEE ALSO
malloc
(3) in UNIX System reference manuals
481
ERROR: Memory allocation failure
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using realloc
() failed while allocating a larger buffer for receiving a message.
ACTION
Make
sure the operating system parameters are set correctly for the amount of memory
on the machine and the amount of memory that can be used by a process. Reduce
the memory usage on the machine or increase the amount of physical memory on
the machine.
SEE ALSO
malloc
(3) in UNIX System reference manuals
482
ERROR: Received message with unknown release number rel_val
DESCRIPTION
The
message received by the BRIDGE was not one from the current release or the
previous one but from release rel_val.
ACTION
Verify
that the releases of the TUXEDO System software installed are valid. Contact
your TUXEDO System Technical Support.
483
ERROR: Shutting down bridge, serious message receive error
DESCRIPTION
The
bridge is shutting down due to a system error.
ACTION
Re-try
the desired operation and if the problem persists, contact your TUXEDO System
Technical Support.
484
ERROR: BRIDGE process detected corrupted message
DESCRIPTION
The
bridge or bootstrap bridge process detected a message with a corrupted header.
This could be caused by problems in the networking software or in TUXEDO
System/T itself.
ACTION
Contact
your TUXEDO System Technical Support for assistance.
485
ERROR: Memory allocation failure
DESCRIPTION
TUXEDO
System/T received an error return while attempting to allocate memory from the
operating system. The amount of memory required by TUXEDO System/T is
influenced by the parameters in the UBBCONFIG file. The number of processes
running on a machine and the options given to those processes also have a large
effect on memory usage.
ACTION
Attempt
to decrease the amount of memory required by TUXEDO System/T, or add more
physical memory to the machine.
SEE ALSO
"TUXEDO
Administrator's Guide"
486
ERROR: Message encoding error
DESCRIPTION
TUXEDO
System/T encountered an error while attempting to encode a negative
acknowledgment message being sent from the bridge or bootstrap bridge process.
ACTION
Contact
your TUXEDO System Technical Support for assistance.
490
ERROR: tprealloc() failed
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using
tprealloc () failed while the system was processing a BRIDGE op-code in
attempting to print BRIDGE statistics.
ACTION
Make
sure the operating system parameters are set correctly for the amount of memory
on the machine and the amount of memory that can be used by a process. Reduce
the memory usage on the machine or increase the amount of physical memory on
the machine.
491
ERROR: tprealloc() failed
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using
tprealloc () failed while the system was processing a BRIDGE op-code.
ACTION
Make
sure the operating system parameters are set correctly for the amount of memory
on the machine and the amount of memory that can be used by a process. Reduce
the memory usage on the machine or increase the amount of physical memory on
the machine.
492
ERROR: tprealloc() failed
DESCRIPTION
An
attempt dynamically to allocate memory from the operating system using
tprealloc () failed while the system was processing a BRIDGE op-code.
ACTION
Make
sure the operating system parameters are set correctly for the amount of memory
on the machine and the amount of memory that can be used by a process. Reduce
the memory usage on the machine or increase the amount of physical memory on
the machine.
493
INFO: Waiting for orderly release to exit
DESCRIPTION
System/T
was processing a server shutdown. This message is an indication of that action.
ACTION
No
action required.
494
INFO: BRIDGE exiting system
DESCRIPTION
System/T
was processing a server shutdown. This message is an indication of that action.
ACTION
No
action required.
495
INFO: Alarm forcing shutdown after 30 second wait
DESCRIPTION
System/T
was processing a BRIDGE shutdown. This message indicates that a forced shutdown
of the BRIDGE was initiated, most likely because a previous network connection
disconnect failed.
ACTION
Please
examine the userlog for further information. If necessary, contact your TUXEDO
System Technical Support.
496
INFO: Rejecting EXIT Message not sent from local BBL or BRIDGE
DESCRIPTION
System/T
was processing a BRIDGE shutdown. The BSBRIDGE process received an EXIT message
from a process other than the local BRIDGE or BBL process, not from a process
on a remote machine.
ACTION
This
message is informative in nature. System/T processing will continue. However,
the userlog may yield additional information that would help explain why this
message was written to the userlog.
497
INFO: Rejecting EXIT Message not sent from local BBL
DESCRIPTION
System/T
was processing a BRIDGE shutdown. The BRIDGE process received an EXIT message
from a process other than the local BBL process, not from a process on a remote
machine.
ACTION
This
message is informative in nature. System/T processing will continue. However,
the userlog may yield additional information that would help explain why this
message was written to the userlog.
498
ERROR: Shutting down bridge, serious message receive error
DESCRIPTION
The
bridge is shutting down due to a system error.
ACTION
Re-try
the desired operation and if the problem persists, contact your TUXEDO System
Technical Support.
499
ERROR: Shutting down bridge, serious message receive error
DESCRIPTION
The
bridge is shutting down due to a system error.
ACTION
Re-try
the desired operation and if the problem persists, contact your TUXEDO System
Technical Support.
CMDTUX Messages 500-599
500
|
ERROR: Shutting
down bridge, serious network error
|
|
Description
|
The bridge is
shutting down due to a network error.
|
|
Action
|
Re-try the desired operation; if the problem persists,
contact your BEA TUXEDO system Technical Support.
|
|
501
|
ERROR: Shutting
down bridge, serious polling error
|
|
Description
|
The bridge is shutting down due to a polling error.
|
|
Action
|
Re-try the desired operation; if the problem persists,
contact your BEA TUXEDO system Technical Support.
|
|
509
|
ERROR: Local
message being nack'd by BRIDGE
|
|
Description
|
The BRIDGE process was incorrectly sent a message destined for a
recipient on the same machine as the sender. It should have been sent
directly to the recipient's UNIX message queue, without any networking or BRIDGE involvement.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
|
511
|
ERROR: Invalid
arguments passed to buildclient
|
|
Description
|
Invalid arguments were passed to the buildclient command.
|
|
Action
|
Correct the arguments to buildclient and reexecute the command.
|
|
See Also
|
buildclient(1)
|
|
512
|
ERROR: Cannot
execute C compiler prog_name
|
|
Description
|
The buildclient command was unable to execute the C compiler. The name of
the program that buildclient attempted to execute is given as part of the error
message.
|
|
Action
|
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.
|
|
See Also
|
buildclient(1)
|
|
520
|
ERROR: Invalid
arguments passed to buildserver
|
|
Description
|
Invalid arguments were passed to the buildserver command.
|
|
Action
|
Correct the arguments to buildserver and reexecute the command. If unsure about the proper
arguments, refer to the on-line usage message.
|
|
See Also
|
buildserver(1)
|
|
522
|
ERROR: buildserver
cannot open the temporary output file, srcfile.
|
|
Description
|
The buildserver cannot open the temporary output file, srcfile.
|
|
Action
|
Check that the directory for the file exists and has write
permissions, and that the file system has sufficient resources for a new
file.
|
|
See Also
|
buildserver(1)
|
|
523
|
WARN: Duplicate
service, svc (function func) is ignored in service dispatch
table.
|
|
Description
|
A service name was specified more than once to the -s option on the command line.
|
|
Action
|
Check your -s option for buildserver and eliminate any duplicate services.
|
|
See Also
|
buildserver(1)
|
|
530
|
ERROR: Cannot
execute prog_name
|
|
Description
|
The buildtms command was unable to execute the buildserver command. The
name of the command being executed is given as part of the error message.
|
|
Action
|
If you are compiling executables to run on the same
machine type, as is normally the case, verify that the TUXDIR shell variable is properly set, that
the program ${TUXDIR}/bin/buildserver exists, is accessible, and executable, and that the shell
variable XCBINDIR is not set.
If you are compiling executables for a different machine
type, verify that the shell variable XCBINDIR is set and exported, and that the program ${XCBINIDIR}/buildserver
exists, is accessible, and executable.
|
|
See Also
|
buildtms(1)
|
|
533
|
ERROR: Cannot be a
cleanupsrv process - Uunixerr Uunixerr_val, errno errno_val
|
|
Description
|
An attempt to execute more than one cleanupsrv process was encountered. If the
process was started from a terminal, then this message appears at the
terminal, otherwise it is written to the userlog. The error can occur when
one or more processes are to be cleaned up and the cleanup doesn't finish
before the next scan by the BBL, causing a second cleanup process to be started.
|
|
Action
|
Retry the desired operation; if the problem persists,
contact your BEA TUXEDO system Technical Support.
|
|
534
|
ERROR: Cannot be a
cleanupsrv process
|
|
Description
|
An attempt to execute more than one cleanupsrv process was encountered. If the
process was started from a terminal, then this message appears at the
terminal, otherwise it is written to the userlog. This can occur when one or
more processes are to be cleaned up and the cleanup doesn't finish before the
next scan by the BBL, causing a second cleanup process to be started.
|
|
Action
|
Retry the desired operation; if the problem persists,
contact your BEA TUXEDO system Technical Support.
|
|
535
|
ERROR: Could not
retrieve server
|
|
Description
|
While attempting to clean up a server, the BEA TUXEDO
system examined system tables located in shared memory to get the entry for
the server. However, the server information could not be found.
|
|
Action
|
Usually, the system will request manual intervention if
this cleanup was not possible for some reason. If further assistance is
needed, please contact the BEA TUXEDO system Administrator.
|
|
536
|
ERROR: Server to be
cleaned up is still running.
|
|
Description
|
A request to clean up a server that was either still
running or in the process of being cleaned up was encountered. Only servers
that are dead may be cleaned up.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
|
537
|
ERROR: Failed to
update server
|
|
Description
|
While cleaning up information about a dead server, the BEA
TUXEDO system was unable to update the server table entry for that server.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
|
538
|
INFO: Process pid
still running - forcing termination (via SIGIOT)
|
|
Description
|
A server that was targeted to be cleaned up was found to
be still running. This message informs the user that the process will be
terminated and a dump of the core will be saved for examination.
|
|
Action
|
Please examine the userlog and the core image saved for
further information. If necessary, contact the BEA TUXEDO system
Administrator.
|
|
539
|
ERROR: Failed to
kill process pid - errmsg
|
|
Description
|
A server that was targeted to be cleaned up was found to
be still running. The BEA TUXEDO system attempted to abort the process and
cause a dump of core to be saved. However, the kill() function failed. The exact message displayed depends upon
the system error that prevented the process from being terminated.
|
|
Action
|
Examine the userlog for other messages about the error. If necessary, contact
the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical
Support.
|
|
540
|
ERROR: Cannot find
Queue Table Entry
|
|
Description
|
A server cleanup was underway. The process had been
terminated if necessary, and the BEA TUXEDO system turned off the information
for that server in the Registry Table, that is, marked it as not restartable.
The system was attempting to retrieve queue information for that server, and
the operation failed.
|
|
Action
|
Examine the userlog for other messages about the error. If necessary, contact
the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical
Support.
|
|
541
|
ERROR: Unable to
decode message header
|
|
Description
|
A server cleanup was underway. The system was attempting
to decode message header information for a message on that server's request
queue, and the operation failed.
|
|
Action
|
Examine the userlog for other messages about the error. If necessary, contact
the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical
Support.
|
|
542
|
ERROR: Cannot find
service to which to forward request
|
|
Description
|
A server cleanup was underway. The system was attempting
to forward a request from the queue of the cleaned-up server. Information for
the service which should be forwarded was missing or unable to be accessed.
|
|
Action
|
Examine the userlog for other messages about the error. If necessary, contact
the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical
Support.
|
|
543
|
ERROR: Cannot
forward message, sending it back
|
|
Description
|
A server cleanup was underway. The system was attempting
to forward a request from the queue of the cleaned-up server. The system call
to enqueue the request failed.
|
|
Action
|
Examine the userlog for other messages about the error. If necessary, contact
the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical
Support.
|
|
544
|
ERROR: Cannot
forward message, sending it back
|
|
Description
|
A server cleanup was underway. The system was attempting
to forward a request from the queue of the cleaned-up server. The system
enqueued the request successfully, but the following function to unlock the
Bulletin Board failed.
|
|
Action
|
Examine the userlog for other messages about the error. If necessary, contact
the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical
Support.
|
|
548
|
ERROR: Cannot
forward message, sending it back
|
|
Description
|
A server cleanup was underway. The system was unable to
forward a message, so the message will be sent back to the sender.
|
|
Action
|
Examine the userlog for other messages about the error. If necessary, contact
the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical
Support.
|
|
550
|
ERROR: Cannot
remove server
|
|
Description
|
A server cleanup was underway. Request and reply queues
had been drained. An attempt to remove the server failed.
|
|
Action
|
Examine the userlog for other messages about the error. If necessary, contact
the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical
Support.
|
|
551
|
INFO: server
removed
|
|
Description
|
A server cleanup was underway. The server was removed
successfully.
|
|
Action
|
Retry the desired operation; if the problem persists,
contact your BEA TUXEDO system Technical Support.
|
|
552
|
WARN: Server
cleanup - server vanished
|
|
Description
|
A server cleanup was underway. The system was scanning the
server table to determine if servers needed cleaning. A server list had been
created that identified the list of servers to be cleaned, but the details on
a particular server could not be obtained from the Server Table. The
processing for this server was skipped.
|
|
Action
|
Retry the desired operation; if the problem persists,
contact your BEA TUXEDO system Technical Support.
|
|
555
|
ERROR: Unable to
reply to pid
|
|
Description
|
A server cleanup was underway. The BEA TUXEDO system was
in the process of draining messages from the server queues, and was
attempting to send a message to the client process informing it that the
server(s) was not alive anymore. The reply failed. The value displayed in
this message indicates the process ID of the process that was to receive the
reply. Often, this implies that a client or server has left the application.
|
|
Action
|
Examine the userlog for other messages about the error. If necessary, contact
the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical
Support.
|
|
556
|
ERROR: Unable to
reset server table entry
|
|
Description
|
A server cleanup was underway. As part of the server
cleanup, the server table entry was to be reset. The function used to reset
this table failed.
|
|
Action
|
Examine the userlog for other messages about the error. If necessary, contact
the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical
Support.
|
|
557
|
ERROR: Automatic
Server Recovery failure; Server processes require manual intervention.
|
|
Description
|
The automatic server recovery has failed. Server processes
will require manual intervention.
|
|
Action
|
Check the userlog for earlier related messages indicating
the nature of the problem. If enough information is provided, it may be
possible to simply re-boot the failed server. Otherwise, you need to manually
shut down the servers and clean up the IPC resources, and then reboot the
servers. See tmboot and tmshutdown for details on BEA TUXEDO system boot and shutdown
procedures.
|
|
See Also
|
tmboot(1), tmshutdown(1)
|
|
560
|
ERROR: Cannot be a
restartsrv process because of an operating system error, Uunixerr_msgerrno_msg
|
|
Description
|
When DBBL scans the Bulletin Board, it will restart any
dead servers that are restartable. However, only one restart process is
allowed at a time. Currently, the restartsrv process cannot join the application due to the operating
system error (TPEOS).
|
|
Action
|
Take proper action according to the errno_msg
and/or Uunixerr_msg, or contact your BEA TUXEDO system Technical
Support.
|
|
561
|
ERROR: Cannot be a
restartsrv process
|
|
Description
|
When DBBL scans the Bulletin Board, it will restart any
dead servers that are restartable. However, only one restart process is
allowed at a time. Currently, the restartsrv process cannot join the application due to an
non-operating system error.
|
|
Action
|
Check the userlog for earlier related messages.
|
|
562
|
ERROR: Cannot
restart a server
|
|
Description
|
Before restarting the server, the server table entry is
retrieved from the Bulletin Board. An error in retrieving the internal server
table entry caused the restartsrv process to fail to restart the server.
|
|
Action
|
Check the current server indicated by the server group and
server identifier global variables. Contact your BEA TUXEDO system Technical
Support.
|
|
563
|
ERROR: Cannot
restart a server
|
|
Description
|
While attempting to restart a server, the restartsrv process was unable to find the queue
entry associated with the server in the internal tables.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
|
564
|
ERROR: Server to be
restarted, pid is still running
|
|
Description
|
While the BBL is scanning the Bulletin Board, it will
restart any dead servers that are restartable. However, the restartsrv process detected that the
restartable server is still alive and running.
|
|
Action
|
The Bulletin Board may be corrupted. Clean up the Bulletin
Board or kill the restartable server and let BBL restart the server. Contact
your BEA TUXEDO system Technical Support.
|
|
565
|
ERROR: Server to be
restarted, pid is still running
|
|
Description
|
While the BBL is scanning the Bulletin Board, it will
restart any dead servers that are restartable. However, the restartsrv process detected that the server
which was marked as non-restartable server is still alive and running.
|
|
Action
|
The Bulletin Board may be corrupted. Clean up the Bulletin
Board. If the server is meant to be restartable, the server should be marked
as "RESTART=Y" in the UBBCONFIG file. Contact your BEA TUXEDO system Technical Support.
|
|
See Also
|
ubbconfig(5)
|
|
566
|
ERROR: Cannot
restart a server because the MAXGEN number reached
|
|
Description
|
Each restartable server can be restarted at most MAXGEN -1 times within the time period
specified by GRACE seconds. Both MAXGEN and GRACE parameters are specified in the SERVERS section of the UBBCONFIG file. Currently, the restartsrv
process failed because it has restarted the server MAXGEN -1 times within the GRACE period.
|
|
Action
|
Check your MAXGEN and GRACE value for each server. Re-boot the server manually with tmboot.
|
|
See Also
|
tmboot(1), ubbconfig(5)
|
|
567
|
ERROR: Cannot
restart the server
|
|
Description
|
The restartsrv process was unable to restart a server because an error
occurred in updating the server entry in the Bulletin Board.
|
|
Action
|
The Bulletin Board may be corrupted. Clean up the Bulletin
Board or contact your BEA TUXEDO system Technical Support.
|
|
568
|
ERROR: Cannot
restart the server
|
|
Description
|
The restartsrv process was unable to restart a server because an error
occurred in getting the server parameters.
|
|
Action
|
The Bulletin Board may be corrupted. Clean up the Bulletin
Board or contact your BEA TUXEDO system Technical Support.
|
|
569
|
ERROR: Cannot
restart the server
|
|
Description
|
The restartsrv process was unable to restart a server because an error
occurred in updating the queue entry in the Bulletin Board.
|
|
Action
|
The Bulletin Board or the server queue may be corrupted.
Clean up the Bulletin Board and the IPCs or contact your BEA TUXEDO system
Technical Support.
|
|
571
|
INFO: Server
process, pid is still running; forcing termination via SIGIOT
|
|
Description
|
As part of restarting a server, the restartsrv process will kill the old server via
SIGIOT and leave a core for debugging.
|
|
Action
|
No action required.
|
|
572
|
ERROR: Cannot kill
the process, pid errno_msg
|
|
Description
|
The restartsrv process failed to kill the old server. The errno_msg
indicates the reason for the failure (based on errno).
|
|
Action
|
Take appropriate action based on the UNIX errno_msg
from kill() or contact your BEA TUXEDO system Technical Support.
|
|
See Also
|
kill(2) in UNIX system reference manuals
|
|
573
|
ERROR: Cannot
restart a server - cannot get information for machine mid
|
|
Description
|
The restartsrv process was unable to restart a server because an error
occurred in retrieving the machine information for mid.
|
|
Action
|
The Bulletin Board may be corrupted. Clean up the Bulletin
Board or contact your BEA TUXEDO system Technical Support.
|
|
574
|
ERROR: Cannot
restart the server - fork error
|
|
Description
|
The restartsrv process cannot fork a new process because the system's
process table is full, or the user is not allowed to create any more
processes, or possibly because of insufficient memory or swap space.
|
|
Action
|
Clean up and verify that the UNIX sysgen process parameters are correct such
as the maximum number of process table entries, the total number of processes
per user, etc. Also, make sure that your machine has sufficient memory or
swap space.
|
|
See Also
|
fork(2) in UNIX system reference manuals
|
|
575
|
ERROR: Cannot
restart a server - exec() failed
|
|
Description
|
The restartsrv process failed to exec() the server because the server executable file is not
found.
|
|
Action
|
Make sure that your server executable files are located
under your application directory specified by the environment variable APPDIR or are in PATH. Make sure that the machine or
server ENVFILE doesn't reset PATH so that the server executable can no longer be found.
|
|
See Also
|
exec(2) in UNIX system reference manuals,
buildserver(1),
ubbconfig(5)
|
|
577
|
ERROR: Cannot
restart the server - no BBL
|
|
Description
|
An attempt to restart a server failed because there is no BBL available.
|
|
Action
|
Check for a partitioned network, corrupted shared memory,
and all administrative processes.
|
|
578
|
ERROR: Cannot
restart the server - no DBBL available
|
|
Description
|
An attempt to restart a server failed because there is no DBBL available.
|
|
Action
|
Check for a partitioned network, corrupted shared memory,
and all administrative processes.
|
|
579
|
ERROR: Cannot
restart a server - unknown process creation error: errno_val
|
|
Description
|
Server restart failed because there is an unknown error
while creating the process.
|
|
Action
|
Take appropriate action based on the UNIX error indicated,
or contact your BEA TUXEDO system Technical Support.
|
|
580
|
INFO: A server
process has restarted: pid
|
|
Description
|
A server process has restarted successfully.
|
|
Action
|
No action required.
|
|
581
|
WARN: Server
restart - server vanished
|
|
Description
|
While scanning the server table to see if other servers
need cleaning, the restartsrv process detected that a server has disappeared from the
internal server table entry.
|
|
Action
|
Shared memory may be corrupted. Contact your BEA TUXEDO
system Technical Support.
|
|
582
|
ERROR: Command line
option formation error for server servername
|
|
Description
|
While formatting the command line options for recreating
the DBBL server's invocation environment for restart, the restartsrv process detected that there are too
many command line options.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
|
583
|
ERROR: Too many
arguments for server servername
|
|
Description
|
The restartsrv process failed to restart a server because the command
line options string for DBBL server is longer than 256 characters and it cannot be
processed.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
|
584
|
ERROR: Restart
error - retrieving server parameters
|
|
Description
|
While examining every entry in the SERVERS section of the
Bulletin Board, an error is encountered while retrieving server parameters.
|
|
Action
|
Check for corrupted shared memory or contact your BEA
TUXEDO system Technical Support.
|
|
585
|
ERROR: Command line
option formation error for server servername
|
|
Description
|
While formatting the command line options for recreating
the server's invocation environment for restart, the restartsrv process detected that there are too
many command line options.
|
|
Action
|
Verify the command line arguments for the server or
contact your BEA TUXEDO system Technical Support.
|
|
586
|
ERROR: Too many
arguments for server servername
|
|
Description
|
The restartsrv process failed to restart the server because the command
line options string for indicated server is longer than 256 characters and it
cannot be processed.
|
|
Action
|
Verify the command line arguments for indicated server or
contact your BEA TUXEDO system Technical Support.
|
|
587
|
INFO: Cannot
restart server, scheduling for cleanup
|
|
Description
|
Some type of transient failure has occurred during the
restart process. The current server is marked as "CLEANING" and it
will be handled by a subsequent cleanupsrv run.
|
|
Action
|
No action required.
|
|
588
|
ERROR: Cannot
retrieve server information for restarting server
|
|
Description
|
For cleanup, we need to find the server table entry for
the current server in the Bulletin Board and update it. However, there is an
error in retrieving the server information from the server table entry.
|
|
Action
|
The shared memory may be corrupted. Contact your BEA
TUXEDO system Technical Support.
|
|
589
|
ERROR: Cannot find
registry table entry for restarting server
|
|
Description
|
The restartsrv process cannot find the registry table entry in the
Bulletin Board for restarting server.
|
|
Action
|
The shared memory may be corrupted. Contact your BEA
TUXEDO system Technical Support.
|
|
590
|
ERROR: Cannot
update server information for restarting server group/id
|
|
Description
|
For cleanup, we need to find the server table entry for
current server in the Bulletin Board and update it. However, there is an
error in updating the server information in the server table entry.
|
|
Action
|
The shared memory may be corrupted. Contact your BEA
TUXEDO system Technical Support.
|
|
592
|
ERROR: Cannot start
the cleanupsrv process: errno_val
|
|
Description
|
The cleanupsrv process can be used by the restartsrv process to remove any dead servers that are not
restartable. However, there is an error in starting the cleanupsrv process with no particular server
indicated.
|
|
Action
|
Check the userlog for earlier related messages.
|
|
593
|
ERROR: Automatic
server recovery failed, server processes require manual intervention
|
|
Description
|
The automatic server recovery has failed. Server processes
will require manual intervention.
|
|
Action
|
Check the userlog for earlier related messages indicating
the nature of the problem. If enough information is provided, it may be
possible to simply re-boot the failed server. Otherwise, you need to manually
shut down the servers and clean up the IPC resources, and then reboot the
servers. See tmboot and tmshutdown for details on BEA TUXEDO system boot and shutdown
procedures.
|
|
See Also
|
tmboot(1), tmshutdown(1)
|
|
594
|
WARN: *Interrupt*
Want to Continue? (y/n):
|
|
Description
|
The restartsrv process has been interrupted by keyboard interrupt
signals.
|
|
Action
|
You can continue with the restartsrv process by entering y or you can stop the restartsrv process by entering n.
|
|
595
|
WARN: Please answer
'y' or 'n'
|
|
Description
|
The restartsrv process has been interrupted. See Message 594 above for
further explanation.
|
|
Action
|
You can continue with the restartsrv process by entering y or you can stop the restartsrv process by entering n.
|
|
No comments:
Post a Comment