CMDTUX Messages 1800-1899

1800

WARN: Server RESTART set to Y and MAXGEN set < 2 on server entry servername

Description

A server entry for servername is configured with the RESTART option but the MAXGEN is set to or defaults to a value less than 2 so that the server will never be restarted.

Action

No action is required. Normally, the MAXGEN value should be set higher so that the server will restart.

See Also

ubbconfig(5)

1801

WARN: Error while parsing filename.

Description

buildserver(1) was parsing the given filename. While parsing the file given via the "-s @filename" option, buildserver encountered a syntax error.

Action

Edit the file specified by the "-s @filename" option. Make sure that each line is a valid argument to the -s option. The file may be commented if the first character of the comment line is "#". Blank lines are also acceptable.

1802

ERROR: Error adding element to heap.

Description

buildserver(1) uses a heap sort algorithm to order the function names. If buildserver(1) was unable to add an element to the heap, then this error will be returned.

Action

If this error occurs consistently, contact BEA TUXEDO system Technical Support.

1803

ERROR: Unable to parse -s option.

Description

While buildserver(1) was parsing the -s option, an error occurred. This error could range anywhere from a syntax error to a file input/output error.

Action

Make sure the -s option has the proper syntax. Also make sure that any file specified with the "-s @filename" option exists and has the proper format.

1804

ERROR: Unable to build function table.

Description

buildserver(1) uses a heap sort in order to manage function names. This error can occur in the second phase of the heap sort if the actual sorted table could not be built.

Action

If this error occurs consistently, contact the

BEA TUXEDO system Technical Support.

1805

WARN: Could not open file filename.

Description

The file specified to buildserver(1) via the "-s @filename" option does not exist.

Action

Make sure that the given filename exists. One useful trick is to specify filename as a full path name, rather than a relative path name.

1806

WARN: File recursion is not supported.

Description

The "-s @filename" option can be used on the command line to buildserver(1). However, the arguments within the file specified by filename cannot specify another file to open and parse. This practice is known as file recursion. File recursion is not supported by buildserver(1).

Action

Remove any lines from filename which begin with the @ character.

1812

WARN: Could not read filetype file filename on LMID

Description

While booting the system or updating the MIB, a security file could not be read on the specified machine. Normally, this will occur when security is configured but one or more of the security files have not been populated (for example, SECURITY is set to USER_AUTH but the group and ACL information is not set).

Action

No action is needed if the associated information is not required for the application.

See Also

ubbconfig(5)

1813

ERROR: Could not encrypt filetype file for propagation to LMID

Description

While booting the system or updating the MIB, a directory needed to hold the security file could not be created.

Action

Verify that the $APPDIR directory exists and has directory permissions that will allow the administrator to create a subdirectory there. Verify that the file system containing $APPDIR has free disk blocks and inodes.

See Also

tmboot (1)

1814

ERROR: Could not propagate filetype file to LMID: Failed to make directory

Description

While booting the system or updating the MIB, a directory needed to hold the file could not be created.

Action

Verify that the $APPDIR directory exists and that directory permissions will allow the administrator to create a subdirectory there. Verify that the file system containing $APPDIR has free disk blocks and inodes.

See Also

tmboot (1)

1815

ERROR: Could not propagate filetype file to LMID: Invalid file type for directory

Description

While booting the system or updating the MIB, a directory needed to hold the file could not be created because a file exists with the same path name.

Action

Remove the file.adm or adm and retry the command.

1816

ERROR: Could not propagate filetype file to LMID: Cannot change mode of directory

Description

While booting the system or updating the MIB, the permissions of a directory needed to hold the file could not be changed.

Action

Change ownership of the adm or .adm directory to the administrative UID.

See Also

ubbconfig(5) MACHINES section

1817

ERROR: Could not propagate filetype file to LMID: Cannot open file

Description

While booting the system or updating the MIB, a security file could not be opened for reading or writing.

Action

Verify that the file system containing $APPDIR has free disk blocks and inodes.

1818

ERROR: Could not propagate filetype file to LMID: Cannot write to file

Description

While booting the system or updating the MIB, a write failed on a security file being propagated to the specified LMID.

Action

Verify that the file system containing $APPDIR has free disk blocks and inodes.

See Also

ubbconfig(5) MACHINES section

1819

ERROR: Could not propagate filetype file to LMID: Error decrypting the file

Description

While booting the system or updating the MIB, there was an encryption problem when propagating one of the security files.

Action

Contact your BEA TUXEDO system Technical Support.

1820

ERROR: Could not propagate filetype file to LMID: Unknown error

Description

While booting the system or updating the MIB, there was an unrecognized return code encountered.

Action

Contact your BEA TUXEDO system Technical Support.

1821

ERROR: MAXACLGROUPS parameter must be > 0 and <= 16384

Description

The MAXACLGROUPS parameter in the RESOURCES section must be greater than 0 and less than 16K. It specifies the maximum number of group identifiers that can be used for ACL permissions checking.

Action

Correct the value of MAXACLGROUPS and re-run tmloadcf(1).

See Also

tmloadcf (1)

1824

ERROR: MAXACLCACHE parameter must be >= 10 and <= 32000

Description

The MAXACLCACHE parameter in the MACHINES section must be greater than or equal to 10 and less than 32000. It specifies the number of entries in the cache used for ACL entries when SECURITY is set to ACL or MANDATORY_ACL.

Action

Correct the value of MAXACLCACHE and re-run tmloadcf(1).

See Also

tmloadcf (1)

1825

ERROR: Current work directory path name is too long

Description

While executing tmloadcf, an attempt to get the current working directory path failed. This can indicate that either the directory pathname is greater than 78 characters in length or that the directory hierarchy is not readable.

Action

Check that the directory hierarchy has the proper permissions and is no longer than 78 characters, and re-execute the command.

1827

ERROR: Absolute path name of the input file is too long

Description

The length of the absolute path name of the input file is greater than MAXTLSTRING.

Action

Specify a shorter path name.

1828

ERROR: Security level must be USER_AUTH, ACL or MANDATORY_ACL.

Description

In order to run tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1), the security level of the BEA TUXEDO application must be USER_AUTH, ACL, or MANDATORY_ACL.

Action

Change the security level in the ubbconfig(5) file to USER_AUTH, ACL, or MANDATORY_ACL. Run tmloadcf(1) on the new ubbconfig(5) file. Then re-run the command that caused this failure.

1829

ERROR: Security level must be USER_AUTH, ACL or MANDATORY_ACL.

Description

In order to run tpusradd(1), tpusrmod(1), or tpusrdel(1), the security level of the BEA TUXEDO application must be USER_AUTH, ACL, or MANDATORY_ACL.

Action

Change the security level in the ubbconfig(5) file to USER_AUTH, ACL, or MANDATORY_ACL. Run tmloadcf(1) on the new ubbconfig(5) file. Then re-run the command that caused this failure.

1830

ERROR: client name is invalid.

Description

The client name given to tpacladd(1), tpaclmod(1), or tpacldel(1) was invalid. A client name must not contain the characters ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.

Action

Change the name given to the command in order to comply with the specifications.

1831

ERROR: new user name is not valid.

Description

The new user name given to tpaclmod(1) or tpacldel(1) was invalid. A user name must not contain the characters '#', ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.

Action

Change the name given to the command in order to comply with the specifications.

1832

ERROR: can't execute command

Description

An error occurred while compiling a server with the buildserver command. The message prints the exact compilation command.

Action

Check the command that it is valid (e.g., files exist and have the correct permissions). Check the errors generated by the compiler and correct them.

See Also

buildserver(1)

1833

ERROR: Group numbers must be between 0 and max.

Description

Group identifiers must be between 0 and 16383. tpgrpadd(1) or tpgrpmod(1) was presented a group number which is not within these boundaries.

Action

Change the group number to be within the proper boundaries. Re-run the command that caused the error.

1834

ERROR: Group numbers must be between 0 and max.

Description

Group identifiers must be between 0 and 16383. tpusradd(1) or tpusrmod(1) was presented a group number which is not within these boundaries.

Action

Change the group number to be within the proper boundaries. Re-run the command that caused the error.

1835

ERROR: Group name is invalid.

Description

The group name given to tpacladd(1), tpaclmod(1), or tpacldel(1) was invalid. A group name must not contain the characters '#', ',', ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.

Action

Change the name given to the command in order to comply with the specifications.