The value specified in the first part of a range entry must be less than or
equal to the value specified in the second part of a range entry.
The value specified in the first part of the range entry was
greater than the value specified in the second part of a range entry.
Recode the range entry so that the first value specified is less than
or equal to the second value.
ubbconfig (5)
In a routing entry, a double quote was found after an odd number of non-escaped
single quotes.
Inspect the single quotes in the flagged routing entry to ensure the
proper format.
ubbconfig (5)
This message is printed as the second part of message 1202.
See message 1196 for an explanation.
This message is printed as the second part of message 1202.
See message 1196 for an explanation.
ubbconfig (5)
See message 1193 for an explanation.
See message 1193 for an explanation.
ubbconfig (5)
The specified entry in the ROUTING section of the UBBCONFIG file contains a
RANGES
entry in which one part of a range is a numeric quantity and
the other part of that range is a string category.
This is not allowed.
Modify the
RANGES
element flagged as being in error so that all
range limits are of the same type and match the type defined for the
field being routed on.
Reload the configuration file.
ubbconfig (5)
A group specified in the
RANGES
parameter for the specified ROUTING
section entry was not defined in the *GROUPS section.
Make sure that the
grpname
flagged as being in error is defined in the *GROUPS section of the UBBCONFIG file.
Check that the two names are spelled the same way.
Also, examine any previous error reported by
tmloadcf
that may have caused the corresponding entry in the *GROUPS section to not
be recognized.
ubbconfig (5)
The ROUTING entry specified contains a
RANGES
value that does not follow the
required format.
Fix the format of the flagged
RANGES
entry.
Often, the format error will be due to a range whose first value
does not start with
MIN ,
a number, or a single quote, a range whose second value does not
start with
MAX ,
a number, or a single quote,
a range which is not followed by a colon,
or a server group name which is not followed by a comma or a double quote
to terminate the
RANGES
entry.
ubbconfig (5)
The ROUTING table entry flagged in the error message has a
BUFTYPE
of
ALL .
This is not allowed.
Specify a specific buffer type for the routing table entry in error,
and reload the configuration file.
ubbconfig (5)
The
BUFTYPE
list specified in an entry in the SERVICES section or in the ROUTING section
of the UBBCONFIG file starts with a comma, or is equal to the null string.
This is not allowed.
Ensure that at least one valid buffer type is specified in the
BUFTYPE
string, and make sure that the string does not begin with a comma.
When the error has been fixed, reload the configuration file.
ubbconfig (5)
The
BUFTYPE
parameter specified in the ROUTING section or SERVICES section
contains one or more null buffer type names.
Change the
BUFTYPE
entry flagged as being in error.
Make certain that the beginning of the
BUFTYPE
string specifies a valid buffer type identifier, and that the string does
not start with a punctuation mark.
Also, make sure that each semicolon in the
BUFTYPE
string is followed by a valid buffer type identifier.
Reload the configuration file.
ubbconfig (5)
The
BUFTYPE
parameter specified in the ROUTING section or SERVICES section of
the UBBCONFIG file contains an unexpected comma.
Change the
BUFTYPE
entry flagged as being in error.
The only places where commas are allowed to occur in
BUFTYPE
entries are between entries of a list of multiple subtypes of a particular
type.
When the error has been fixed, the configuration file should
be reloaded.
ubbconfig (5)
One of the buffer type names specified in the
BUFTYPE
parameter of a SERVICES section or ROUTING section entry of the UBBCONFIG file
exceeds the maximum allowed length.
The maximum allowed length of a buffer type name is 8 bytes.
Change the buffer type name so that it is no longer than 8 bytes, and
reload the configuration file.
ubbconfig (5)
The
BUFTYPE
parameter specified in an entry in
the ROUTING section or SERVICES section of the UBBCONFIG file
contains an unexpected colon or comma.
Examine the
BUFTYPE
entry flagged as being in error to determine the exact problem.
A colon may occur only between a name of a type and the name of the
first acceptable subtype.
A comma may occur only between names of subtypes.
When the error has been corrected, reload the configuration file.
ubbconfig (5)
The
BUFTYPE
parameter specified in an entry in
the ROUTING section or SERVICES section of the UBBCONFIG file
contains a null buffer subtype name.
This may occur when a colon or comma is followed by another punctuation
mark without any intervening subtype name.
Fix any subtype list which ends in a comma.
Specify one or more subtypes for any type which requires a subtype,
and do not follow any type which does not accept subtypes with a colon.
When done, reload the configuration file.
ubbconfig (5)
One of the buffer subtype names specified in the
BUFTYPE
parameter of a SERVICES section or ROUTING section entry of the UBBCONFIG file
exceeds the maximum allowed length.
The maximum allowed length of a buffer subtype name is 16 bytes.
Change the buffer subtype name so that it is no longer than 16 bytes, and
reload the configuration file.
ubbconfig (5)
A subtype list contained within the
BUFTYPE
parameter of a SERVICES section or ROUTING section entry of the UBBCONFIG file
specified both the wild-card subtype '*' and a specific subtype name.
This is not allowed.
If the application should accept all subtype names,
specify '*' without specifying any specific subtype names.
If the application should accept only specific subtype names,
remove '*' from the list of subtype names.
When the change has been made, reload the configuration file.
ubbconfig (5)
The
BUFTYPE
parameter of a ROUTING section entry of the UBBCONFIG file
specified '*' as a buffer subtype.
This is not allowed.
If routing on a view, specify the specific buffer type to be routed on.
If routing on an
FML
buffer, no buffer subtypes are allowed.
Reload the configuration file once it has been modified.
ubbconfig (5)
The
BUFTYPE
parameter of a SERVICES section entry or ROUTING section entry in the
UBBCONFIG file specified duplicate type/subtype pairs.
(For types without any subtype specified, the
BUFTYPE
parameter specified duplicate type pairs.)
Modify the
BUFTYPE
parameter so that the same type/subtype pair is not specified more than once.
Reload the configuration file.
ubbconfig (5)
If multiple entries exist in the SERVICES section with the same service name
but with different
SRVGRP
parameters, the
BUFTYPE
parameter must be the same for all of the entries.
This rule was violated for the service entry named in the error message.
Specify the same
BUFTYPE
parameters for all instances of a particular service name.
Then reload the configuration file.
ubbconfig (5)
If a service has multiple entries in the SERVICES
section (for different
SRVGRP
parameters),
all entries must have the same
BUFTYPE
parameter.
Modify all entries for
service
so that the
BUFTYPE
parameter is consistent.
ubbconfig (5)
The maximum number of type/subtype combinations that
a service can accept was exceeded.
This is a fixed limit that requires a recompiled TUXEDO System version to increase.
Contact your TUXEDO System Technical Support.
Other options are:
Reduce the number of type/subtype combinations by using
"*" for a subtype wildcard.
Have the server process call
tptypes ()
on its input buffer,
and enforce its own rules concerning allowed buffer type/subtype combinations.
tptypes (3),
ubbconfig (5)
While executing
tmconfig ,
the program was unable to get the password entry based on the
current user identifier.
Make sure that a password entry exists for the administrator
who is running the
tmconfig
command.
Contact your TUXEDO System Technical Support.
tmconfig (1)
While executing
tmconfig ,
an operating system error occurred while attempting to determine the level
of authentication required by the application configuration.
A code is printed indicating the specific UNIX System call which failed.
These codes may be referenced in the header file <Uunix.h> .
Attempt to determine why the UNIX System call is failing.
Often, this error will occur if the
TUXCONFIG
shell variable is not set consistently in this process and the rest of
the application.
tmconfig (1),
tpchkauth (3)
The
tpchkauth()
function returned an error when called by
tmconfig
to determine the level of authentication required by the application
configuration.
Attempt to determine why the
tpchkauth()
function call is failing.
Often, this will be due to an incorrect
setting of the
TUXCONFIG
shell variable.
tmconfig (1),
tpinit (3)
When writing out the current buffer values,
tmconfig
was unable to create and open a temporary file for writing
(in the current directory for DOS, or
/tmp
for TUXEDO System).
Check that the directory has write
and execute permissions set correctly, and that the file system has
the proper resources for creating and writing a file.
tmconfig (1)
An attempt to dynamically allocate memory from the operating system using
realloc ()
failed while
creating an internal data structure related to
TMS
boot or shutdown.
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.
A temporary work-around is to require less space
by booting or shutting down one machine, group,
or server at a time.
tmboot (1)
If any group on a machine has a
TMS
specified, the
TLOGDEVICE
parameter in the *MACHINES section
must be set.
Modify the configuration file.
ubbconfig (5)
The
BRIDGE
process could not establish its listening address
for incoming network connections.
Check the
NADDR
and
BRIDGE
parameters for this
machine in the *NETWORK section of the configuration file.
ubbconfig (5),
*NETWORK section
The
BRIDGE
process' networking device pathname
is set incorrectly, or the device does not exist.
Modify the
BRIDGE
parameter for this machine
in the configuration file's
*NETWORK section.
ubbconfig (5),
*NETWORK section
The
SECURITY
parameter in the *RESOURCES section of the configuration
file is invalid.
Modify the configuration file.
ubbconfig (5)
An unexpected error occurred when attempting to create a randomly
generated encryption key.
Contact your TUXEDO System Technical Support.
An unexpected error occurred when attempting to encrypt
the application security password.
Contact your TUXEDO System Technical Support.
1201 ERROR: *ROUTING entry entry_name does not meet the requirement that the lower limit of every range must be less than or equal to the upper limit
DESCRIPTION
ACTION
SEE ALSO
1202 ERROR: *ROUTING entry entry_name needs a single quote at the end of a character string
DESCRIPTION
ACTION
SEE ALSO
1203 ERROR: or a backslash to escape a double quote.
DESCRIPTION
ACTION
SEE ALSO
1204 ERROR: *ROUTING entry entry_name has both numeric and character values in the RANGES statement
DESCRIPTION
ACTION
SEE ALSO
1205 ERROR: *ROUTING entry entry_name mixes a numeric value with a string value in a RANGES statement
DESCRIPTION
ACTION
SEE ALSO
1206 ERROR: *ROUTING entry entry_name contains an invalid group name grpname.
DESCRIPTION
ACTION
SEE ALSO
1207 ERROR: *ROUTING entry entry_name contains an invalid RANGES value.
DESCRIPTION
ACTION
SEE ALSO
1208 ERROR: *ROUTING entry entry_name specifies an illegal BUFTYPE of ALL
DESCRIPTION
ACTION
SEE ALSO
1209 ERROR: Buffer types in section_name entry entry_name start with ',' or null
DESCRIPTION
ACTION
SEE ALSO
1210 ERROR: section_name entry entry_name contains a null buffer type name
DESCRIPTION
ACTION
SEE ALSO
1211 ERROR: section_name entry entry_name contains an unexpected comma
DESCRIPTION
ACTION
SEE ALSO
1212 ERROR: section_name entry entry_name contains an excessively long type name type_name
DESCRIPTION
ACTION
SEE ALSO
1214 ERROR: section_name entry entry_name contains an unexpected colon or comma
DESCRIPTION
ACTION
SEE ALSO
1215 ERROR: section_name entry entry_name contains a null buffer subtype name
DESCRIPTION
ACTION
SEE ALSO
1216 ERROR: section_name entry entry_name contains excessively long subtype name subtype_name
DESCRIPTION
ACTION
SEE ALSO
1217 ERROR: section_name entry entry_name specified both '*' and a specific subtype name
DESCRIPTION
ACTION
SEE ALSO
1218 ERROR: *ROUTING entry entry_name specifies '*' where it is not allowed
DESCRIPTION
ACTION
SEE ALSO
1221 ERROR: section_name entry entry_name contains a duplicate type(type_name)/subtype(subtype_name) pair
DESCRIPTION
ACTION
SEE ALSO
1225 ERROR: *SERVICES entry entry_name does not have the same BUFTYPE for all entries of this service.
DESCRIPTION
ACTION
SEE ALSO
1228 ERROR: section entry service must have the same BUFTYPE for all *SERVICE entries
DESCRIPTION
ACTION
SEE ALSO
1229 ERROR: section entry service too many buffer type/subtypes specified
DESCRIPTION
ACTION
SEE ALSO
1231 ERROR: Unable to get user id
DESCRIPTION
ACTION
SEE ALSO
1232 ERROR: tpchkauth failed - Uunixerr = code
DESCRIPTION
ACTION
SEE ALSO
1233 ERROR: Cannot determine authentication level
DESCRIPTION
ACTION
SEE ALSO
1237 ERROR: Can't open filename
DESCRIPTION
ACTION
SEE ALSO
1267 ERROR: Cannot start/stop servers, Memory allocation failure
DESCRIPTION
ACTION
SEE ALSO
1268 ERROR: GROUP entry, group, TMS specified and LMID, lmid, does not have TLOGDEVICE
DESCRIPTION
ACTION
SEE ALSO
1270 ERROR: Could not establish network address - check device and address
DESCRIPTION
ACTION
SEE ALSO
1271 ERROR: Invalid BRIDGE device pathname
DESCRIPTION
ACTION
SEE ALSO
1273 ERROR: Invalid option string, for SECURITY keyword
DESCRIPTION
ACTION
SEE ALSO
1275 ERROR: Cannot create encryption key
DESCRIPTION
ACTION
1276 ERROR: Cannot create encryption schedule for application password
DESCRIPTION
ACTION