Skip navigation.

CMDTUX Messages 6700-6799

  Previous Next

6701

ERROR: Current working directory path name is too long

Description

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

Action

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

6702

ERROR: Cannot obtain absolute repository input file path

Description

While executing tmloadrepos, an attempt to get the absolute repository input file path failed. This file is given as an argument in the -i command line option, which can either be an absolute path or a relative path.

Action

Check that a valid repository input file path is given, and re-execute the command.

See Also

tmloadrepos(1)

6703

ERROR: Absolute repository input file path is too long

Description

The length of the absolute repository input file path name is greater than MAXTLSTRING. This file is given as an argument in the -i command line option.

Action

Specify a shorter path name.

See Also

tmloadrepos(1)

6704

ERROR: Repository file must be specified

Description

While executing tmloadrepos, repository file path was not included.

Action

Specify a repository file path in the command line.

See Also

tmloadrepos(1)

6705

ERROR: Cannot obtain absolute repository file path

Description

While executing tmloadrepos, an attempt to get the absolute repository file path failed. This file is given as an argument without a command line option. It can either be an absolute path or a relative path.

Action

Check that a valid repository file path is given, and re-execute the command.

See Also

tmloadrepos(1)

6706

ERROR: Absolute repository file path is too long

Description

The length of the absolute repository path name is greater than MAXTLSTRING. This file is given as an argument without a command line option.

Action

Specify a shorter path name.

See Also

tmloadrepos(1)

6707

ERROR: Cannot use the -e and -d options together

Description

The -e and -d options used in tmloadrepos are mutually exclusive. The -e option is used to replace all pre-existing repository information. The -d option is used to delete specified service(s) from the repository.

Action

Change the arguments in the tmloadrepos command so that the -e and -d options are not both specified and re-execute the command.

See Also

tmloadrepos(1)

6708

ERROR: Cannot use the -i and -d options together

Description

The -i and -d options used in tmloadrepos are mutually exclusive. The -i option is used to specify an input file for creating and loading service information to a new repository or to modify an existing one. The -d option is used to delete specified service(s) from an existing repository.

Action

Change the arguments in the tmloadrepos command so that the -i and -d options are not both specified and re-execute the command.

See Also

tmloadrepos(1)

6709

ERROR: Service list string cannot be greater than MAXTLSTRING characters

Description

The service list string is given as an argument in the -d command line option. If more than one service is deleted, use character ',' as the separator. The length of the service list string is greater than MAXTLSTRING.

Action

Specify fewer services to delete from the repository.

See Also

tmloadrepos(1)

6710

Usage: tmloadrepos [-e | -d service1[,...]] [-y] [-i repository_input] repository_file

Description

Invalid use of tmloadrepos.

Action

Follow the "Usage:" hint.

See Also

tmloadrepos(1)

6711

ERROR: filename is a Jolt repository file or an old format metadata repository file

Description

The given repository is a Jolt repository file or an old format metadata repository file which cannot be modified with tmloadrepos directly.

Action

Check that the correct repository file path is given, and re-execute the command. A Jolt repository file or an old format metadata repository file cannot be modified directly. You may first use tmunloadrepos to unload the text version service metadata definition from the given repository file and then load a new binary metadata repository file with tmloadrepos.

See Also

tmloadrepos(1), tmunloadrepos(1)

6712

ERROR: Repository file filename does not exist

Description

While executing tmloadrepos to delete services, the given repository file does not exist.

Action

Check that the repository file path points to a valid existing file, and re-execute the command.

6713

ERROR: Repository file filename has invalid format

Description

tmloadrepos detected the given repository file exists, but is in an invalid format.

Action

Check that the correct repository file path points to a properly formatted file. Make sure that the repository file is not corrupt and re-execute the command.

6714

ERROR: Memory allocation error when opening repository file filename

Description

An attempt to dynamically allocate memory from the operating system using calloc() failed while opening the specified repository file.

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 and/or swap space on the machine.

6715

ERROR: Error reading repository file filename

Description

An attempt to read the repository file failed while deleting specified services using tmloadrepos. The error might be a system disk IO error, a dynamic memory allocation error, or a corrupt repository file.

Action

Make sure the operating system parameters are set correctly for the file IO and the working directory hierarchy has the right permissions for the existing file. Make sure the operating system parameters are set correctly for the amount of memory required. Make sure the repository file is not corrupt.

6716

ERROR: Error creating repository file filename

Description

While executing tmloadrepos, the specified repository file does not exist. An attempt to create a new repository file failed. The error might be a system disk IO error or a dynamic memory allocation error.

Action

Make sure the operating system parameters are set correctly for the file IO and the working directory hierarchy has the right permissions to create a binary file. Make sure the operating system parameters are set correctly for the amount of memory required.

6717

ERROR: Error creating temporary repository file filename

Description

While executing tmloadrepos with -e option, an attempt to create a temporary repository file failed. The error might be a system disk IO error or a dynamic memory allocation error.

Action

Make sure the operating system parameters are set correctly for the file IO and the working directory hierarchy has the right permissions to create a binary file. Make sure the operating system parameters are set correctly for the amount of memory required.

6718

ERROR: Error reading repository input file filename

Description

An attempt to access specified repository input file failed.

Action

Check if the repository file exists with the correct permissions and normal status.

6719

ERROR: Error creating new repository file filename

Description

While executing tmloadrepos, the specified repository file does not exist. An attempt to creat the repository file failed. The error might be a system disk IO error or a dynamic memory allocation error.

Action

Make sure the operating system parameters are set correctly for the file IO and the working directory hierarchy has the correct permissions to create a binary file. Make sure the operating system parameters are set correctly for the amount of memory required.

6720

INFO: Service servicename deleted...

Description

Service deletion prompt.

Action

None.

6721

INFO: Service servicename not found...

Description

Service not found prompt.

Action

None.

6722

INFO: Service servicename delete error...

Description

Service deletion failed prompt.

Action

None.

6723

ERROR: Memory allocation error when parsing the service input file

Description

An attempt to dynamically allocate memory from the operating system using calloc() failed when reading and parsing service definitions from the repository input file.

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 and/or swap space on the machine.

6724

ERROR: Repository input file filename does not exist

Description

The specified repository input file does not exist.

Action

Check that the repository input file path points to a valid existing file and re-execute the command.

6725

ERROR: Repository file filename is locked by another program

Description

tmloadrepos detected another METADATA utility is using the specified repository file. The utility might be a TMMETADATA(5) server, a tmunloadrepos(1) command, another tmloadrepos(1) command or a customer program written with ATMI functions tpgetrepos(3c)/tpsetrepos(3c).

Action

Check all other utilities that are using the specified repository file. Wait for them to quit and then re-execute the command.

6726

ERROR: Cannot obtain absolute .SCD service output file path

Description

While booting TMMETADATA server process, an attempt to get the absolute service contract discovery output file path failed. This file is given as an argument with the -o option. It can either be an absolute path or a relative path.

Action

Make sure a valid service contract discovery output file path is given to configure TMMETADATA(5) and then reboot the application.

See Also

TMMETADATA(5)

6727

ERROR: Absolute .SCD output file path is too long

Description

The length of absolute service contract discovery output file path name is greater than MAXTLSTRING. This file is given as an argument with the -o option in the TUXCONFIG file to configure TMMETADATA(5).

Action

Specify a shorter path name.

See Also

TMMETADATA(5)

6728

ERROR: Open .SCD output file filename failure

Description

TMMETADATA failed to create and open the specified service contract discovery output file for writing.

Action

Check that the directory for the output file exists and has write and execute permissions set correctly.

See Also

TMMETADATA(5)

6730

ERROR: Cannot read predefined FML field when opening repository file filename

Description

An attempt to read predefined FML fields failed when opening repository. The predefined FML fields used by metadata repository are located in the $TUXDIR/udataobj/tpadm file.

Action

Make sure environment variable TUXDIR is set correctly and $TUXDIR/udataobj/tpadm can be accessed.

See Also

METAREPOS(5)

6731

ERROR: Current working directory path name is too long

Description

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

Action

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

6732

ERROR: Repository file must be specified

Description

While executing tmunloadrepos, repository file path was not included.

Action

Specify a repository file path to the command line.

See Also

tmunloadrepos(1)

6733

ERROR: Cannot obtain absolute repository file path

Description

While executing tmunloadrepos, an attempt to get the absolute repository file path failed. This file is given as an argument with no command line option, which can be either a absolute path or or a relative path.

Action

Check that a valid repository file path is given, and re-execute the command.

See Also

tmunloadrepos(1)

6734

ERROR: Absolute repository file path is too long

Description

The length of the absolute repository path name is greater than MAXTLSTRING. This file is given as an argument without a command line option. It can either be an absolute path or a relative path.

Action

Specify a short path name.

See Also

tmunloadrepos(1)

6735

ERROR: Cannot use the -option1 and -option2 options together

Description

While executing tmunloadrepos, the -t, -w and -c options can be used to specify output format of tmunloadrepos. These three options are mutually exclusive.

Action

Change the arguments in the tmunloadrepos command so that the -t, -w and -c options are not specified simultaneously and re-execute the command.

See Also

tmunloadrepos(1)

6736

ERROR: The service regular expression list cannot be greater than MAXTLSTRING characters

Description

The service regular expression list is given as an argument in the -s command line option. If more than one service regular expression is specified, use character ',' as the separator. The length of the list is greater than MAXTLSTRING.

Action

Specify a smaller service regular expression list.

See Also

tmunloadrepos(1)

6737

Usage: tmunloadrepos [-s service_regular_expression1[,...]] [-t|-c] repository_file

Description

Invalid usage of tmunloadrepos.

Action

Follow the "Usage:" hint.

See Also

tmunloadrepos(1)

6738

ERROR: Repository file filename does not exist

Description

tmunloadrepos detected the given repository file does not exist.

Action

Check that the repository file path points to a valid existing file, and re-execute the command.

6739

ERROR: Repository file filename has invalid format

Description

tmunloadrepos detected the given repository file exists but is in an invalid format.

Action

Check that the repository file path points to a properly formatted, valid existing file. Make sure that the repository file is not corrupt and re-execute the command.

6740

ERROR: Memory allocation error when opening repository file filename

Description

An attempt to dynamically allocate memory from the operating system using calloc() failed while opening the specified repository file.

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 and/or swap space on the machine.

6741

ERROR: Error reading repository file filename

Description

An attempt to read the repository file failed while executing tmunloadrepos. The error might be a system disk IO error, a dynamic memory allocation error, or a corrupt repository file.

Action

Make sure the operating system parameters are set correctly for the file IO and the working directory hierarchy has the correct permissions for the existing file. Make sure the operating system parameters are set correctly for the amount of memory required. Make sure the repository file is not corrupt.

6742

ERROR: Memory allocation error when unloading service information

Description

An attempt to dynamically allocate memory from the operating system using calloc() failed when preparing memory for unloading service information from the repository file.

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 and/or swap space on the machine.

6743

ERROR: Memory allocation error when reading service servicename

Description

An attempt to dynamically allocate memory from the operating system using calloc() failed when reading service servicename from the repository file.

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 and/or swap space on the machine.

6744

ERROR: Service servicename information may be corrupt

Description

tmunloadrepos detected the service servicename information stored in the repository is corrupt.

Action

Use tmloadrepos to reload the correct service servicename information into the repository.

See Also

tmloadrepos(1)

6745

ERROR: Service servicename information is illegal

Description

tmunloadrepos detected that the service servicename information is illegal. The repository file may be corrupt.

Action

Use tmloadrepos to reload the correct service servicename information into the repository.

See Also

tmloadrepos(1)

6746

ERROR: No matching services in repository file filename

Description

Cannot find any service in the repository file with the specified service regular expression.

Action

Change the service regular expression and re-execute the command.

6747

ERROR: '-opt' option is not supported by tmunloadrepos

Description

-opt option is not supported by tmunloadrepos. The valid options are -t, -w and -c.

Action

Use one of the following options: -t, -w and -c for service output.

See Also

tmunloadrepos(1)

6748

ERROR: XML generator initialization failed: detail-msg

Description

An attempt to initialize XML DOM tree generator failed, see detail-msg for further information. This may be caused by a memory allocation error or a Xerces library internal error.

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 and/or swap space on the machine. See Xerces reference for other Xerces errors.

6749

ERROR: XML generator initialization failed: DOM Exception code is errcode

Description

An attempt to initialize XML DOM tree generator failed, see errcode for further information. Xerces library throws a DOM Exception.

Action

See Xerces reference for DOM Exception.

6750

ERROR: Adding service(servicename) to DOM Tree failed

Description

An attempt to add service servicename information into a Xerces DOM Tree failed. This error is generated by Xerces Library.

Action

Use another service regular expression and re-execute the command. If the problem persists, contact BEA Customer Support.

6751

ERROR: Creating XML output failed: detail-msg

Description

An attempt to initialize XML output generator failed, see detail-msg for further information. This may be caused by a memory allocation error or a Xerces library internal error.

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 and/or swap space on the machine. See Xerces reference for other Xerces error.

6752

ERROR: Creating XML output failed: DOMException code is : errcode

Description

An attempt to create XML output generator failed, see errcode for further information. Xerces library throws a DOM Exception.

Action

See Xerces reference for DOM Exception.

6753

ERROR: Error setting read-locking occurred when opening repository file filename

Description

tmunloadrepos detected another tmloadrepos program is using the same repository file.

Action

Wait for the tmloadrepos program to quit and then re-execute the command.

6754

ERROR: System error when opening repository file filename

Description

While executing tmunloadrepos, an unknown system error is encountered when opening the repository file.

Action

Contact BEA Customer Support.

6755

ERROR: Error setting read-locking occurred when reading repository file filename

Description

While executing tmunloadrepos, an attempt to set read-locking to the repository file failed. Another METADATA program is using the same repository file.

Action

Check and stop all abnormal utilities that are accessing the repository file and then re-execute the command.

6756

WARN: Current working directory path name is too long

Description

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

Action

Make sure that the directory hierarchy has the proper permissions and is not longer than MAXTLSTRING characters. Reboot the application.

6757

ERROR: Cannot obtain absolute repository file path

Description

While booting TMMETADATA server process, an attempt to get the absolute repository file path failed. This file is given as an argument with the -f option. It can either be an absolute path or a relative path.

Action

Make sure a valid repository file path is given to configure TMMETADATA(5) and then reboot the application.

See Also

TMMETADATA(5)

6758

ERROR: Absolute repository file path is too long

Description

The length of absolute repository file path name is greater than MAXTLSTRING. This file is given as an argument with the -f option in the TUXCONFIG file to configure TMMETADATA(5).

Action

Specify a shorter path name.

See Also

TMMETADATA(5)

6759

WARN: Invalid command line argument 'opt' ignored

Description

Invalid option is given in the TUXCONFIG file to configure TMMETADATA.

Action

Modify the TUXCONFIG file and then reboot the application.

See Also

TMMETADATA(5)

6760

ERROR: -f option is not specified

Description

The -f option was not specified when configuring TMMETADATA in the TUXCONFIG file.

Action

Modify the TUXCONFIG file, specify the repository file path with -f option to TMMETADATA(5) and then reboot the application.

See Also

TMMETADATA(5)

6761

ERROR: Repository file filename does not exist

Description

TMMETADATA detected the given repository file path points to a non-existing file.

Action

Modify the TUXCONFIG file, make sure the repository file path points to a valid existing file and then reboot the application.

See Also

TMMETADATA(5)

6762

ERROR: Repository file filename has invalid format

Description

TMMETADATA detected the given repository file exists, but is in an invalid format.

Action

Modify the TUXCONFIG file, make sure the repository file path points to a valid existing file and then reboot the application.

See Also

TMMETADATA(5)

6763

ERROR: System error when opening repository file filename

Description

An unknown system error was encountered when TMMETADATA opens the repository file.

Action

Contact BEA Customer Support.

6764

ERROR: A TMMETADATA server with write permission is running, the TMMETADATA server with read-only permission cannot boot

Description

An attempt to boot a TMMETADATA server with read-only permission failed because another TMMETADATA process with write permission is running.

Action

Modify the TUXCONFIG, configure all TMMETADATA servers with the same read or write permission.

See Also

TMMETADATA(5)

6765

WARN: Cannot advertise .REPROLOCK service

Description

An attempt to advertise .REPROLOCK service failed.

Action

Shutdown application, reconfigure the UBBCONFIG by increasing MAXSERVICES and MAXACCESSES. Then try to reboot. If the problem persists, contact BEA Customer Support.

See Also

UBBCONFIG(5)

6766

ERROR: A TMMETADATA server with read-only permission is running, the TMMETADATA server with write permission cannot boot

Description

An attempt to boot the TMMETADATA server with write permission failed because another TMMETADATA process with read-only permission is running.

Action

Modify the TUXCONFIG, configure all TMMETADATA servers with the same read or write permission.

See Also

TMMETADATA(5)

6767

WARN: Cannot advertise .REPWRLOCK service

Description

An attempt to advertise .REPWRLOCK service failed.

Action

Shutdown application, reconfigure the UBBCONFIG by increasing MAXSERVICES and MAXACCESSES. Then try to reboot. If the problem persists, contact BEA Customer Support.

See Also

UBBCONFIG(5)

6768

ERROR: Cannot advertise .TMMETAREPOS service

Description

An attempt to advertise .TMMETAREPOS service failed.

Action

Shutdown application, reconfigure the UBBCONFIG by increasing MAXSERVICES and MAXACCESSES. Then try to reboot. If the problem persists, contact BEA Customer Support.

See Also

UBBCONFIG(5)

6769

INFO: TMMETADATA server started with repository file filename

Description

The TMMETADATA boot was started successfully.

Action

None.

6770

INFO: TMMETADATA tpsvrdone complete

Description

The TMMETADATA server has shutdown successfully.

Action

None.

6771

ERROR: Invalid operation (TA_OPERATION) specified for METAREPOS request

Description

An invalid generic MIB field TA_OPERATION value is set in a METAREPOS request.

Action

Set one of the following three values: GET/SET/GETNEXT.

See Also

MIB(5),METAREPOS

6772

ERROR: Repository file filename is a Jolt repository file or an old format metadata repository file

Description

The TMMETADATA process with write permission detected the given repository file is a Jolt repository file or an old format metadata repository file.

Action

Modify the UBBCONFIG, change the repository file to a new format metadata repository file or change the TMMETADATA as a process with read-only permission.

See Also

TMMETADATA(5)

6773

ERROR: .TMMETAREPOS only has read permission to the repository file

Description

A METAREPOS set operation failed. This may be caused by either the TMMETADATA process being a read-only permission process or the specified repository file is a Jolt repository file.

Action

A Jolt repository file cannot be modified using Service Metadata Repository utilities. To modify a metadata repository file, please change the TMMETADATA server section to have write permission in the TUXCONFIG file.

See Also

TMMETADATA(5)

6774

ERROR: Error reading repository file filename

Description

An attempt to read the repository file failed when TMMETADATA server was booting. The error may be a system disk IO error, a dynamic memory allocation error or a corrupt repository file.

Action

Make sure the operating system parameters are set correctly for the file IO and the working directory hierarchy has the correct permissions for the existing file. Make sure the operating system parameters are set correctly for the amount of memory required. Make sure the repository file is not corrupt.

6775

ERROR: Repository file filename is locked by another program

Description

While booting the TMMETADATA server, another tmloadrepos program using the same repository file was detected.

Action

Wait for the tmloadrepos program to quit and then reboot the application.

6776

ERROR: Repository file is locked by another program

Description

While TMMETADATA server is processing a request, an attempt to set read-locking to the repository file failed. Another tmloadrepos program is using the same repository file.

Action

Check all abnormal utilities that are modifying the repository file and stop them. Then try to resend the request to TMMETADATA.

6777

ERROR: System error when synchronizing repository file information

Description

While TMMETADATA server was processing a request, an unknown system error was encountered when reading the repository file.

Action

Try to resend the request to .TMMETAREPOS. If the problem persists, contact BEA Customer Support.

6778

ERROR: Cannot read predefined FML field

Description

An attempt to read predefined FML fields failed when opening repository in TMMETADATA server. The predefined FML fields used by metadata repository are located in the $TUXDIR/udataobj/tpadm file.

Action

Make sure environment variable TUXDIR is set correctly and $TUXDIR/udataobj/tpadm can be accessed.

See Also

METAREPOS(5)

 

Skip footer navigation  Back to Top Previous Next