System Messages: CMDSCA Catalog 200-299


200	*ERROR: There can only be one composite specified when target component is specified for programname.*
	Description	If the `buildscacomponent`(1) `-c` option argument contains a '/', it is interpreted as the name of a composite followed by the name of a composite. When this syntax is used, it is permissible to specify only one composite.
	Action	Fix the syntax of the `buildscacomponent`(1) `-c` option and re-execute the command.
	See Also	`buildscacomponent`(1)
201	*ERROR: programname* does not support target component in composite list.**
	Description	The `buildscaserver`(1) command does not support the composite/component syntax for the `-c` option, although this syntax is supported by `buildscacomponent`(1). The only syntax allowed for the `buildscaserver`(1) `-c` option is a comma separated list of one or more composite names.
	Action	Fix the syntax of the `buildscacomponent`(1) `-c` option and re-execute the command.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
202	ERROR: TUXDIR environment variable not set.
	Description	The required environment variable TUXDIR was not set when invoking `buildscacomponent`(1) or `buildscaserver`(1).
	Action	Set TUXDIR to the directory where Tuxedo is installed and re-invoke `buildscacomponent`(1) or `buildscaserver`(1).
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
203	*ERROR: SystemConfigurationException(exception_text).*
	Description	An exception occurred while invoking `buildscacomponent`(1) or `buildscaserver`(1).
	Action	Refer to the exception_text to determine the specific action to take.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
204	*WARN: More than one composite file with name compositename* is found, only the first one is used.**
	Description	The `-c` option to the `buildscacomponent`(1) or `buildscaserver`(1) specified more than one composite file with the same name compositename. Only the first such file is processed.
	Action	Either accept the output of the command as is, or specify compositename only once and rerun the command.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
205	*WARN: Requested composite compositename* not found!**
	Description	The `-c` option to the `buildscacomponent`(1) or `buildscaserver`(1) specified composite file compositename, but that file was not found.
	Action	Ensure that the composite file specified by the `-c` option exists and rerun the command.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
206	WARN: No requested composite found, processing stopped.
	Description	None of the composite files specified by the `buildscacomponent`(1) or `buildscaserver`(1) `-c` exist. As a result, no libraries or executables is generated.
	Action	Ensure that the composite file(s) specified by the `-c` option exist and rerun the command.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
207	*ERROR: Unable to load file compositefile.*
	Description	The composite file compositefile used as input to `buildscacomponent`(1) or `buildscaserver`(1) did not contain any root data object. As a result, the file could not be loaded.
	Action	Ensure that the contents of compositefile are valid and rerun the command.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
208	ERROR: Unable to load composite: exception_text
	Description	An exception occurred while `buildscacomponent`(1) or `buildscaserver`(1) was loading a composite file.
	Action	Refer to exception_text for details of the specific problem.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
209	WARN: The requested composite compositename is not defined in root composite rootname.composite in directory directoryname
	Description	The root composite rootname`.composite` does not containe compositename as one of the composites listed under the root for directory directoryname.
	Action	Either fix the root composite to include compositename or fix the value of compositename if it is incorrect.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
210	*WARN: No ATMI service defined in composite compositename.*
	Description	No ATMI service was defined as part of composiste compositename.
	Action	If it is desired that this component process ATMI services, then specify one or more ATMI services as part of the composite.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
211	WARN: No operation found in WSDL: wsdlname for port type porttype
	Description	No WSDL operation was found in Web Services Definition Language file wsdlname.
	Action	Fix the WSDL syntax and re-execute `buildscacomponent`(1) or `buildscaserver`(1).
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
212	ERROR: Unable to load or parse WSDL wsdlname; could not find port type porttype
	Description	Web Services Definition Language file wsdlname could not be loaded or parsed due to the invalid port type porttype.
	Action	Fix the WSDL syntax and re-execute `buildscacomponent`(1) or `buildscaserver`(1).
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
213	ERROR: Unable to load or parse WSDL: wsdlname
	Description	An error occurred while loading or parsing the Web Service Definition Language file wsdlname.
	Action	Ensure that wsdlname conforms to proper WSDL syntax.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
214	ERROR: Unable to load or parse WSDL: wsdlname
	Description	An error occurred while loading or parsing the Web Service Definition Language file wsdlname. This message is followed by message CMDSCA_CAT:215.
	Action	Ensure that wsdlname conforms to proper WSDL syntax.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
215	ERROR: Exception: exception_text
	Description	An SDO runtime exception occurred while loading or parsing the Web Service Definition Language file wsdlname. This message is preceded by message CMDSCA_CAT:214.
	Action	Refer to exception_text for details of the specific problem.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
217	ERROR: Incorrect number of arguments passed
	Description	`scapasswordtool`(1) was invoked with an incorrect number of arguments. A usage message is printed following this message showing the correct arguments.
	Action	Fix the incorrect arguments and re-invoke `scapasswordtool`(1).
	See Also	`scapasswordtool`(1)
218	ERROR: Invalid option passed
	Description	`scapasswordtool`(1) was invoked with an invalid option. A usage message is printed following this message showing the correct arguments.
	Action	Fix the invalid option and re-invoke `scapasswordtool`(1).
	See Also	`scapasswordtool`(1)
219	ERROR: Identifier too long. Please enter an identifier of at most 40 characters.
	Description	The identifier specified by the `scapasswordtool`(1) `-i` passwordidentifier exceeds the maximum allowable length of 40 characters.
	Action	Fix the incorrect passwordidentifier and make sure it matches the value specified in the \ element of SCDL files.
	See Also	`scapasswordtool`(1)
220	ERROR: The password.store file does not exist.
	Description	The `scapasswordtool`(1) `-d` option was used to delete an identifier from an existing password store, but no `password.store` file exists in the current directory.
	Action	Invoke `scapasswordtool`(1) from the directory where the `password.store` file is located.
	See Also	`scapasswordtool`(1)
221	*ERROR: The identifier passwordidentifier* already exists. Please delete it first.**
	Description	The `scapasswordtool`(1) `-a` option was used to add a password identifier, but passwordidentifier already exists in the `password.store` file in the current directory.
	Action	If the password for passwordidentifier is to be changed, this identifier must first be deleted from the password store and then re-added.
	See Also	`scapasswordtool`(1)
222	*ERROR: Identifier passwordidentifer* not found.**
	Description	The `scapasswordtool`(1) `-d` option was used to delete an identifier from an existing password store, but passwordidentifier was not found in the `password.store` file.
	Action	Check that passwordidentifier has been typed correctly. If `passwordidentifier has been typed correctly, no action is required, since this identifier never existed or has already been deleted.`
	See Also	`scapasswordtool`(1)
225	ERROR: Unable to obtain password
	Description	An error occurred while `scapasswordtool`(1) was reading a password from the terminal.
	Action	Make sure that a password is typed at the terminal before hitting the enter key.
	See Also	`scapasswordtool`(1)
226	ERROR: Passwords are not identical
	Description	The passwords supplied to `scapasswordtool`(1) at the "Enter password:" prompt and the "Confirm password:" prompts were not identical.
	Action	Make sure that the password and its confirmation are typed correctly.
	See Also	`scapasswordtool`(1)
227	ERROR: Password too long
	Description	The password supplied to `scapasswordtool`(1) exceeds the maximum allowable length.
	Action	Re-invoke `scapasswordtool`(1) and use a shorter password.
	See Also	`scapasswordtool`(1)
228	ERROR: Cannot generate key
	Description	An error occurred when `scapasswordtool`(1) attempted to generate a cryptographic key corresponding to the entered password.
	Action	Contact your Oracle SALT support organization.
	See Also	`scapasswordtool`(1)
229	ERROR: Cannot encrypt data
	Description	An error occurred when `scapasswordtool`(1) attempted to encrypt password data.
	Action	Contact your Oracle SALT support organization.
	See Also	`scapasswordtool`(1)
230	ERROR: Cannot decrypt data
	Description	An error occurred when `scapasswordtool`(1) attempted to decrypt password data.
	Action	Contact your Oracle SALT support organization.
	See Also	`scapasswordtool`(1)
231	*ERROR: Cannot rename tempfile* as file (errno=errno)**
	Description	An error occurred when `scapasswordtool`(1) attempted to rename the temporary file tempfile as file. The operating system value of errno is included to help in diagnosis of the problem.
	Action	Verify that there is space on the current filesystem and that the current user has permission to create file and to delete tempfile.
	See Also	`scapasswordtool`(1)
244	*ERROR: Method overloading is not supported.(methodname)*
	Description	When invoking `buildscacomponent`(1) or `buildscaserver`(1), more than one definition was found for method methodname.
	Action	Ensure that there is only one definition for each method in SCA component files.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
245	*ERROR: Multiple targets mapped to the same TUXEDO service not allowed.(svcname)*
	Description	When invoking `buildscacomponent`(1) or `buildscaserver`(1), more than one target was found mapping to the same Tuxedo service svcname.
	Action	Ensure that at most one target maps to each Tuxedo service in SCA component files.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
246	*ERROR: Invalid method specified in map.(methodname)*
	Description	When invoking `buildscacomponent`(1) or `buildscaserver`(1), an invalid method methodname was found in a \ method.
	Action	Ensure that only valid methods are used in SCA component files.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
249	ERROR: found portType porttype in service svcname, but namespaces do not match: portType namespace: portnamespace, namespace URI in SCDL namespaceuri
	Description	The namespace for a service portType does not match the namespace configured in the corresponding SCDL file
	Action	Fix the incorrect namespace parameter.
	See Also	`buildscacomponent`(1), `buildscaserver`(1)
250	*ERROR: SCA root(scaroot) is not a valid directory.*
	Description	The SCA root directory specified to `buildscaclient`(1) using the `-s` scaroot parameter or using the APPDIR environment variable is a type of file other than a directory, or the current user cannot change directory to this directory.
	Action	Ensure that scaroot is a directory and that the current user has permission to change directory to this directory.
	See Also	`buildscaclient`(1)
251	*ERROR: programname* must be started from component directory.**
	Description	The `buildscaclient`(1) command must be invoked from the directory where the component file for the client being built is located.
	Action	Change directory to the proper directory and re-invoke `buildscaclient`(1).
	See Also	`buildscaclient`(1)
252	*ERROR: SCA root(scaroot) does not exist.*
	Description	The SCA root directory specified to `buildscaclient`(1) using the `-s` scaroot parameter or using the APPDIR environment variable does not exist.
	Action	Ensure that scaroot exists and is a directory.
	See Also	`buildscaclient`(1)
253	ERROR: Undetermined exception occurred, process terminated.
	Description	An exception occurred during the execution of `buildscaclient`(1)
	Action	Examine other error messages to determine the cause of the error. Executing `buildscaclient`(1) with the `-v` option will print additional information about the operation of `buildscaclient`(1).
	See Also	`buildscaclient`(1)
254	ERROR: Errors encountered while loading composite file compositefile
	Description	Errors occurred while parsing compsite file compositefile
	Action	Ensure that compositefile has proper syntax for a composite file.
	See Also	`buildscaclient`(1)
255	*Component componentname* not found**
	Description	`buildscaclient`(1) was unable to find the component specified by the `-c` componentname option
	Action	Ensure that componentname exists and re-execute `buildscaclient`(1).
	See Also	`buildscaclient`(1)