---

15. CMDTUX Messages 1400-1499

---

1401	ERROR: buildclient cannot open the temporary output file, srcfile
	Description	The buildclient 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	buildclient(1)
1402	INFO: SRVID = srvid, SRVGRP = grpname, SIGKILL sent
	Description	A SIGKILL signal was sent to a server in response to a tmshutdown -w command.
	Action	No action required.
	See Also	tmshutdown(1)
1403	INFO: SRVID = srvid, SRVGRP = grpname, SIGKILL send failed (tperrno = tperrno_val NETerr = number)
	Description	A SIGKILL signal could not be sent to a server in response to a tmshutdown -w command. A likely cause is that the server has already exited due to tmshutdown 's message or previously sent SIGTERM signal.
	Action	No action required.
	See Also	tmshutdown(1)
1407	INFO: SRVID = srvid, SRVGRP = grpname, SIGTERM sent
	Description	A SIGTERM signal was sent to a server in response to a tmshutdown -w command.
	Action	No action required.
	See Also	tmshutdown(1)
1409	WARN: Could not mark receive queue
	Description	The BRIDGE process could not mark its receive message queue, probably because the BSBRIDGE did not exit as expected after helping boot the BBL.
	Action	The BRIDGE will continue running, and the system should recover automatically. Kill the BSBRIDGE process manually if it is still running.
1410	ERROR: Could not mark receive queue
	Description	The BSBRIDGE process determined that another process is unexpectedly reading from its request message queue. Perhaps there is another BSBRIDGE or BRIDGE running. A BSBRIDGE experiencing this error will fail its initialization routine, and will exit.
	Action	If the machine fails to boot, run tmboot to try again, or run tmshutdown to clean up.
	See Also	tmboot(1), tmshutdown(1)
1411	ERROR: Could not reattach to bulletin board
	Description	A BRIDGE or BSBRIDGE was unexpectedly booted with PROTECTED access to its bulletin board area of shared memory. It could not reattach in FASTPATH mode. It will fail initialization, and then exit.
	Action	Contact your BEA TUXEDO system Technical Support.
	See Also	ubbconfig(5)
1413	ERROR: Could not get network device name
	Description	A BRIDGE or BSBRIDGE system process could not find a networking device name: the BRIDGE parameter in the NETWORK section. It will fail initialization, and then exit.
	Action	Check the NETWORK section of the system configuration file. Contact your BEA TUXEDO system Technical Support.
	See Also	ubbconfig(5)
1414	ERROR: Could not shut down BSBRIDGE
	Description	The BRIDGE system process could not send a message to the BSBRIDGE telling it to shut down. The BRIDGE will fail its initialization, and then exit.
	Action	Run tmshutdown on the machine to remove the BSBRIDGE. If this does not work, kill it manually. Then attempt another tmboot.
	See Also	tmboot(1), tmshutdown(1)
1417	ERROR: Cannot check BBL, Memory allocation failure
	Description	While attempting to check the local BBL 's sanity, the BRIDGE system process could not dynamically allocate memory from the operating system using malloc(). The BRIDGE will continue running, but the BBL will not be restarted if it dies.
	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.
1418	ERROR: Cannot retrieve BBL server table entries
	Description	While attempting to check the local BBL 's sanity, the BRIDGE could not find a server table entry for it. The BRIDGE will continue running, but the BBL will not be restarted if it dies.
	Action	Run tmshutdown and tmboot for this machine. Contact your BEA TUXEDO system Technical Support.
	See Also	tmboot(1), tmshutdown(1)
1419	ERROR: Cannot retrieve local BBL's queue table entry
	Description	While attempting to check the local BBL 's sanity, the BRIDGE could not find a queue table entry for it. The BRIDGE will continue running, but the BBL will not be restarted if it dies.
	Action	Run tmshutdown and tmboot for this machine. Contact your BEA TUXEDO system Technical Support.
	See Also	tmboot(1), tmshutdown(1)
1420	ERROR: Cannot restart local BBL
	Description	While attempting to check the local BBL 's sanity, the BRIDGE detected that it is dead, and attempted a restart. The restart failed. The BRIDGE will continue running, and will continue to attempt to restart the BBL.
	Action	Run tmshutdown and tmboot for this machine. Contact your BEA TUXEDO system Technical Support.
	See Also	tmboot(1), tmshutdown(1)
1421	ERROR: Can allow only release 4.2.1 (or later) BBLs to join system with a configuration of 50 machines or more
	Description	A BBL for a machine that is running a release of the software prior to 4.2.1 is trying to join the application. This will fail because the configuration has more than 50 machines, which is not supported for earlier versions of the software.
	Action	Upgrade the software on the machine to Release 4.2.1 or later.
1422	ERROR: failed to restart administrative server, rescheduling restart.
	Description	The restartsrv command was unable to restart an administrative server (BBL or BRIDGE). The command has been scheduled to be restarted during the next cycle.
	Action	Check for subsequent userlog messages indicating whether or not the server was restarted.
1423	ERROR: Pipe error, assume failed.
	Description	While restarting a BEA TUXEDO system process, restartsrv received a pipe signal and the system issues this message to point out that it is not aware of the process status. Normally, this indicates that the process was not started successfully.
	Action	Check the userlog for additional messages indicating the status of the process being restarted. If this is an application server, check for application messages and/or a core dump in the APPDIR directory. If this is a system server, contact your BEA TUXEDO system Technical Support.
1424	ERROR: Failed to start BSBRIDGE
	Description	The restartsrv command failed to restart the boot-strap bridge server.
	Action	Check the userlog for prior messages indicating the nature of the failure. Contact your BEA TUXEDO system Technical Support.
1427	ERROR: Shutting down BBL due to removal of message queue
	Description	The UNIX System message queue used by the BBL process to receive messages has been removed. Since retrying the failed message receive operation will not correct this error, the BBL is exiting. This condition can occur if the BEA TUXEDO system administrator or a UNIX System privileged user has manually removed IPC resources using the UNIX System ipcrm(1) command. Depending upon the extent of IPC resources which were removed, other BEA TUXEDO system system process may also print similar messages in the userlog.
	Action	The administrator should use tmboot to reboot the BEA TUXEDO system configuration on the node where IPC resources were removed. If only a subset of the BEA TUXEDO system IPC resources have been removed, it is possible that the reboot will fail. In this case, it will be necessary to manually kill the remaining BEA TUXEDO system processes and to manually remove any IPC resources with a key equal to the value specified for IPCKEY in the BEA TUXEDO system configuration file. The UNIX System ipcrm(1) command may be used to manually remove IPC resources.
	See Also	BEA TUXEDO Administrator's Guide, tmboot(1), kill(1), and ipcrm(1) in UNIX system reference manuals
1428	ERROR: Bad header from network, mid=0xmidval
	Description	The BRIDGE process received a network message that is directed toward another machine, midval, or the message header was corrupted. The network connection will be dropped.
	Action	The connection will be re-established when needed. No action required.
1429	INFO: Forcing check of all BBLs
	Description	The DBBL got a bbclean request to check the sanity of all BBL processes on all machines.
	Action	No action required.
1430	ERROR: Failed to suspend local BRIDGE(s) for partitioned shutdown
	Description	While trying to suspend the local BRIDGE process during a partitioned shutdown request, an error occurred.
	Action	Check the userlog for error messages to clarify the problem. If the cause cannot be discerned, contact your BEA TUXEDO system Technical Support.
	See Also	tmshutdown(1)
1431	ERROR: -P option cannot specify remote LMID
	Description	While executing tmshutdown, a remote LMID value was specified for the -P option.
	Action	Re-execute the command using a local LMID for the -P option.
	See Also	tmshutdown(1)
1432	INFO: pclean - lmid now reachable and not removed from bulletin board
	Description	A request to clean up the specified lmid was processed by the DBBL and found that the machine that had been partitioned can now be contacted and the BBL process on the machine is alive.
	Action	The entries for the machine will not be removed from the Bulletin Board.
	See Also	tmadmin(1)
1433	INFO: pclean - lmid not partitioned and not removed from bulletin board
	Description	A request to clean up the specified lmid was processed by the DBBL and found that the machine was not marked as partitioned.
	Action	The entries for the machine will not be removed from the Bulletin Board.
	See Also	tmadmin(1)
1434	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using malloc() failed while allocating space to hold the compilation parameters in buildclient or buildclt.
	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.
1435	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using malloc() failed while allocating space to hold the compilation parameters in buildclient or buildclt.
	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.
1436	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using malloc() failed while allocating space to hold the command line parameters in buildserver.
	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.
1437	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to generate the command line to compile the server in buildserver.
	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.
1438	ERROR: *ROUTING entry entry_name - only VIEW, FML, X_C_TYPE, or X_COMMON type is allowed in ROUTING section
	Description	The configuration file ROUTING section entry named in the error message specified a BUFTYPE entry of a buffer type that is not VIEW, FML, X_C_TYPE, or X_COMMON.
	Action	Modify the ROUTING section entry in error to specify a valid type.
	See Also	ubbconfig(5)
1439	ERROR: section entry name: Must have subtype for VIEW, X_C_TYPE, and X_COMMON
	Description	While executing tmloadcf, an entry for name in the ROUTING or SERVICES section as indicated by section has a BUFTYPE value with type VIEW, X_C_TYPE, or X_COMMON that does not have a subtype specified.
	Action	Correct the BUFTYPE parameter on the entry and re-execute the command.
	See Also	ubbconfig(5)
1440	ERROR: section entry name: Can't have subtype for FML, STRING, CARRAY, or X_OCTET
	Description	While executing tmloadcf, an entry for name in the ROUTING or SERVICES section as indicated by section has a BUFTYPE value with type FML, STRING, CARRAY, or X_OCTET that has a subtype specified. This is not valid.
	Action	Correct the BUFTYPE parameter on the entry and re-execute the command.
	See Also	ubbconfig(5)
1443	ERROR: can't attach to BB
	Description	While trying to shut down the DBBL in an MP configuration, tmshutdown was unable to properly set up a private copy of the Bulletin Board.
	Action	Contact your BEA TUXEDO system Technical Support.
	See Also	tmshutdown(1)
1444	ERROR: TUXCONFIG environment variable must be an absolute pathname.
	Description	While executing tmboot or tmshutdown, the TUXCONFIG environment variable was not set and exported, or was not set to an absolute pathname (starting with /).
	Action	Set and export the TUXCONFIG environment variable and re-execute the command.
	See Also	tmboot(1), tmshutdown(1)
1445	ERROR: TUXCONFIG environment variable must be an absolute pathname.
	Description	While executing tmloadcf, the TUXCONFIG environment variable was not set and exported, or was not set to an absolute pathname (starting with /).
	Action	Set and export the TUXCONFIG environment variable and re-execute the command.
	See Also	tmloadcf(1)
1446	ERROR: TUXCONFIG environment variable must be an absolute pathname.
	Description	While executing tmunloadcf, the TUXCONFIG environment variable was not set and exported, or was not set to an absolute pathname (starting with /).
	Action	Set and export the TUXCONFIG environment variable and re-execute the command.
	See Also	tmunloadcf(1)
1447	ERROR: Cannot open TLOG temporary dump file pathname, errno=errno_val
	Description	A temporary file necessary for loading data into the TLOG device could not be opened (for creation).
	Action	Check the permissions, free disk blocks, and free inodes for the directory where the temporary file was to be created.
1448	ERROR: Cannot write TLOG temporary dump file pathname, errno=errno_val
	Description	A temporary file necessary for loading data into the TLOG device could not be written.
	Action	Check the permissions, free disk blocks, and free inodes for the directory where the temporary file was to be written.
1449	ERROR: Cannot close TLOG temporary dump file pathname, errno=errno_val
	Description	A temporary file necessary for loading data into the TLOG device could not be closed.
	Action	Check the permissions, free disk blocks, and free inodes for the directory where pathname resides.
1450	ERROR: Cannot open temporary TLOG dump file pathname, errno=errno_val
	Description	A temporary file necessary for loading data into the TLOG device could not be opened (for reading).
	Action	Check the file and directory permissions.
1451	ERROR: MAXACCESSERS parameter must be greater than MAXWSCLIENTS
	Description	The value for MAXACCESSERS as specified in the RESOURCES or MACHINES section of the UBBCONFIG file, is less than or equal to MAXWSCLIENTS.
	Action	Correct the value for MAXACCESSERS or MAXWSCLIENTS.
	See Also	ubbconfig(5)
1452	ERROR: Unexpected end-of-input - exiting
	Description	While executing tmconfig, end-of-input was encountered (for example, end of file or control-D) and the program exits.
	Action	Re-run the program providing the correct input.
	See Also	tmconfig(1)
1453	ERROR: Invalid input - exiting
	Description	While executing tmconfig, an invalid input value was entered and the program is not attached to a terminal (that is, the standard input and output are not associated with a terminal). The program will exit.
	Action	Correct the input stream or file and re-run the program.
	See Also	tmconfig(1)
1454	ERROR: tpchkauth failed - Uunixerr = code
	Description	While executing ud, 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>.
	Action	Attempt to determine why the UNIX 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.
	See Also	ud(1), tpchkauth(3c)
1455	ERROR: can't create buffer - tpalloc() failed - errmsg
	Description	While executing ud, tpalloc failed to allocate a typed buffer. The nature of the failure is indicated by errmsg.
	Action	The tpalloc(3c) manual page lists the specific reasons why tpalloc may fail.
	See Also	ud(1), tpalloc(3c)
1456	ERROR: can't become a client - tpinit() failed - errmsg
	Description	While executing ud, tpinit failed in trying to join the application. The nature of the failure is indicated by errmsg.
	Action	The tpinit(3c) manual page lists the specific reasons why tpinit may fail.
	See Also	ud(1), tpinit(3c)
1457	ERROR: tpalloc for TPINIT failed - errmsg
	Description	While executing ud, tpalloc failed to allocate a TPINIT typed buffer. The nature of the failure is indicated by errmsg.
	Action	The tpalloc(3c) manual page lists the specific reasons why tpalloc may fail.
	See Also	ud(1), tpalloc(3c)
1458	ERROR: Can't start a transaction - tpbegin() failed - errmsg
	Description	ud attempted to start a transaction and was unsuccessful. Further information is indicated by the string errmsg.
	Action	The tpbegin(3c) manual page contains a description of each error value returned.
	See Also	ud(1), tpbegin(3c)
1459	ERROR: Can't commit transaction, tpcommit() failed - errmsg
	Description	ud encountered an error while attempting to commit a transaction. Quite often, the failure of the transaction commit is due to the failure of one or more of the service participants, or due to transaction timeout. Further information is indicated by the errmsg string.
	Action	The tpbegin(3c) manual page lists the specific reasons why tpcommit may fail.
	See Also	ud(1), tpbegin(3c)
1460	ERROR: tpalloc for TPINIT failed - errmsg
	Description	While executing tmconfig, tpalloc failed to allocate a TPINIT typed buffer. The nature of the failure is indicated by errmsg.
	Action	The tpalloc(3c) manual page lists the specific reasons why tpalloc may fail.
	See Also	tmconfig(1), tpalloc(3c)
1461	ERROR: can't become a client - tpinit() failed - errmsg
	Description	While executing tmconfig, tpinit failed in trying to join the application. The nature of the failure is indicated by errmsg.
	Action	The tpinit(3c) manual page lists the specific reasons why tpinit may fail.
	See Also	tmconfig(1), tpinit(3c)
1462	ERROR: can't create buffer - tpalloc() failed - errmsg
	Description	While executing tmconfig, tpalloc failed to allocate an FML typed buffer. The nature of the failure is indicated by errmsg.
	Action	The tpalloc(3c) manual page lists the specific reasons why tpalloc may fail.
	See Also	tmconfig(1), tpalloc(3c)
1467	ERROR: System unstable - reboot recommended
	Description	The DBBL got an error while dispatching an administrative service. This usually indicates an internal problem.
	Action	Reboot the application. If the problem persists, contact your BEA TUXEDO system Technical Support.
1468	INFO: Listener Process Started
	Description	The tlisten process was able to start and establish a listening endpoint on the network. The user may check the tlisten log file for log connections and services data.
	Action	No action required.
	See Also	tlisten(1)
1469	ERROR: realloc() failed
	Description	While executing tmloadcf, an attempt dynamically to re-allocate memory from the operating system using realloc() failed in the lexical analyzer.
	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 reference manuals, ubbconfig(5)
1470	WARN: Function name must be <= len characters in length; name will be truncated
	Description	The function name, name, specified using the -s option on the command line of buildserver, is greater than the allowed function name length, len, and will be truncated. This will restrict the ability of this service to be dynamically advertised at run-time.
	Action	Choose a shorter function name if this function will be dynamically advertised at run-time.
	See Also	buildserver(1)
1472	ERROR: MIN is greater than MAX on server entry servername; MAX is set to the same value as MIN
	Description	While executing tmloadcf, an entry for servername in the SERVERS section has a MIN value that is greater than the MAX value.
	Action	Correct the MIN or MAX parameter on the entry and re-execute the command.
	See Also	ubbconfig(5)
1473	ERROR: -c and {A|B|D|M|S|T|e|g|i|l|o|s|w|y}
	Description	While executing tmboot, the -c option was specified with another option. The -c option should normally be specified by itself.
	Action	Re-execute the command with the correct command line options.
	See Also	tmboot(1)
1478	WARN: ROUTING routingname (for SERVICE servicename) is not defined in the ROUTING section
	Description	An entry for service servicename in the SERVICES section of the UBBCONFIG file has a ROUTING value of routingname that does not appear in the RESOURCES section of the configuration file. This situation is allowed if the application is providing its own buffer-type routing function for the associated service. Messages will fail to be sent to the service if the application does not provide a routing function.
	Action	No action is needed if an application-provided routing function exists. Otherwise, an entry should be added in the ROUTING section of the configuration file.
	See Also	ubbconfig(5), typesw(5)
1479	ERROR: Memory allocation failure
	Description	While executing tmloadcf, an attempt dynamically to allocate memory from the operating system using realloc() 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.
	See Also	malloc(3) in UNIX reference manuals, ubbconfig(5)
1480	WARN: MIN/MAX greater than 1 and RQADDR not specified on conversational server entry servername
	Description	An entry in the SERVERS section of the UBBCONFIG file for a conversational server, servername, has a MIN or MAX value that is greater than 1, but the RQADDR value is not specified. Normally, a set of conversational servers are used in an MSSQ set, that is, they share a request queue, and this is configured by specifying an RQADDR value.
	Action	If an MSSQ set is desired, then specify an RQADDR value for the server entry in the UBBCONFIG file.
	See Also	ubbconfig(5)
1481	ERROR: Can't have NETWORK section in SHM mode
	Description	A NETWORK section exists in a UBBCONFIG file that has SHM specified for the MODEL in the RESOURCES section.
	Action	Change the MODEL to MP if the application consists of multiple machines connected via a network, or delete the NETWORK section from the UBBCONFIG file.
	See Also	ubbconfig(5)
1482	WARN: OPENINFO/CLOSEINFO ignored for GROUP groupname
	Description	An entry for group groupname in the GROUPS section of the UBBCONFIG file has OPENINFO and/or CLOSEINFO but the group is not associated with a resource manager (that is, TMSNAME is "TMS" or not specified). The OPENINFO and CLOSEINFO parameter value will be ignored.
	Action	No action required.
	See Also	ubbconfig(5)
1483	WARN: can't contact local tlisten process
	Description	While booting a configuration with tmboot, the local tlisten process could not be contacted. This probably means that tlisten is not running on the MASTER machine. In this case, tmadmin can run only in read-only mode on remote machines and it will not be possible for the backup site to become the master site.
	Action	Start tlisten on the MASTER machine.
	See Also	tlisten(1), tmboot(1)
1484	ERROR: end of input reached without terminating double quote
	Description	While processing a UBBCONFIG file with tmloadcf, the end of the file was reached with a double-quoted string not terminated.
	Action	Go to the last unescaped, double quote in the file and add a matching double quote at the end of the string. Re-execute the command.
	See Also	ubbconfig(5)
1485	ERROR: end of input reached without terminating double quote
	Description	While processing a UBBCONFIG file with tmloadcf, the end of the file was reached without terminating a double-quoted string (that is, the string was started with a double quote but the matching double quote was not found).
	Action	Go to the last unescaped, double quote in the file and add a matching double quote at the end of the string. Re-execute the command.
	See Also	ubbconfig(5)
1486	ERROR: AUTOTRAN specified for SERVICE servicename SRVGRP groupname with no TMS.
	Description	An entry for service servicename with group name groupname in the SERVICES section of the UBBCONFIG file has the AUTOTRAN parameter set to Y but the group is not associated with a resource manager (that is, TMSNAME is not set).
	Action	Either set the AUTOTRAN parameter to N or associate the service with a group that has a resource manager.
	See Also	ubbconfig(5)
1487	WARN: AUTOTRAN specified for SERVICE servicename with TRANTIME=0.
	Description	An entry for service servicename in the SERVICES section of the UBBCONFIG file has the AUTOTRAN parameter set to Y but an unlimited transaction timeout value. This can be dangerous because the automatically started transactions will not timeout in the event of failures.
	Action	It is recommended that a transaction timeout value be specified.
	See Also	ubbconfig(5)
1488	WARN: REPLYQ=Y not specified for MSSQ server servername
	Description	An entry for server servername in the SERVERS section of the UBBCONFIG file has an RQADDR value specified forming an MSSQ set, but does not have a reply queue specified (REPLYQ is set to N or not specified). Normally, all servers in an MSSQ need their own reply queue such that they share the input request queue but each gets back responses to outgoing requests on its own reply queue.
	Action	It is recommended that REPLYQ=Y be added to the server entry.
	See Also	ubbconfig(5)
1489	WARN: dubious escape character
	Description	While processing a string or character constant in a UBBCONFIG file, a backslash followed by character was found which is not one of the recognized escape sequences (for example, backspace, form feed, tab, newline, or octal value). The character will be treated as itself and the backslash is ignored.
	Action	No action required.
	See Also	ubbconfig(5)
1490	WARN: character escape octal_value does not fit in character
	Description	While processing a string or character constant in a UBBCONFIG file, a backslash followed by an octal value, octal_value, was found whose value is greater than the value that can fit into a character (that is, e377). The value will be truncated (that is, octal_value e377).
	Action	No action required.
	See Also	ubbconfig(5)
1491	ERROR: UID parameter must be >= 0 and <= 2147483647
	Description	The value for UID as specified in the RESOURCES section of the UBBCONFIG file is less than 0 or greater than 2147483647. UID must be greater than or equal to 0 and less than or equal to 2147483647.
	Action	Correct the value for UID as specified in the RESOURCES section of the UBBCONFIG file to be greater than or equal to 0 and less than or equal to 2147483647.
	See Also	ubbconfig(5)
1492	ERROR: GID parameter must be >= 0 and <= 2147483647
	Description	The value for GID as specified in the RESOURCES section of the UBBCONFIG file is less than 0 or greater than 2147483647. GID must be greater than or equal to 0 and less than or equal to 2147483647.
	Action	Correct the value for GID as specified in the RESOURCES section of the UBBCONFIG file to be greater than or equal to 0 and less than or equal to 2147483647.
	See Also	ubbconfig(5)
1493	ERROR: UID parameter must be >= 0 and <= 2147483647
	Description	The value for UID as specified in the MACHINES section of the UBBCONFIG file is less than 0 or greater than 2147483647. UID must be greater than or equal to 0 and less than or equal to 2147483647.
	Action	Correct the value for UID as specified in the MACHINES section of the UBBCONFIG file to be greater than or equal to 0 and less than or equal to 2147483647.
	See Also	ubbconfig(5)
1494	ERROR: GID parameter must be >= 0 and <= 2147483647
	Description	The value for GID as specified in the MACHINES section of the UBBCONFIG file is less than 0 or greater than 2147483647. GID must be greater than or equal to 0 and less than or equal to 2147483647.
	Action	Correct the value for GID as specified in the MACHINES section of the UBBCONFIG file to be greater than or equal to 0 and less than or equal to 2147483647.
	See Also	ubbconfig(5)

---

---