STG Messages 0-99
|
|
1
Unexpected error occurred while runnning the scatuxgen tool. The Java exception is below.
Description
An unexpected error occurred while processing a composite or interface file.
Action
Contact Oracle Technical Support.
2
Cannot process both SCA composite file name (-c) and an interface header (-i).
Description
The scatuxgen command was passed both a composite file name and an interface header name. The command is designed to process one or the other.
Action
Either specify the name of a composite file using the -c switch, or the name of an interface header using the -i switch.
3
Please provide a SCA composite file name (-c) or an interface header (-i).
Description
The scatuxgen command was neither passed a composite file name nor an interface header name. The command is designed to process one or the other.
Action
Either specify the name of a composite file using the -c switch, or the name of an interface header using the -i switch.
4
Please provide a service name (-s)
Description
No service name was specified for this command.
Action
Specify a service name.
5
Invalid buffer type for -I option
Description
An invalid buffer type name was passed using the -I switch.
Action
Valid values are: STRING, CARRAY, X_OCTET, VIEW, X_C_TYPE, X_COMMON, VIEW32, FML, FML32, MBSTRING or XML
6
Invalid buffer type for -O option
Description
An invalid buffer type name was passed using the -O switch.
Action
Valid values are: STRING, CARRAY, X_OCTET, VIEW, X_C_TYPE, X_COMMON, VIEW32, FML, FML32, MBSTRING or XML
7
Invalid buffer type for -E option
Description
An invalid buffer type name was passed using the -E switch.
Action
Valid values are: STRING, CARRAY, X_OCTET, VIEW, X_C_TYPE, X_COMMON, VIEW32, FML, FML32, MBSTRING or XML
8
No subtype name provided for input buffer passed in -I option
Description
A buffer type of VIEW, X_C_TYPE, X_COMMON, VIEW32, FML or FML32 requires a subtype name to indicate the type of complex data used.
Action
Qualify the type with a subtype using the notation
9
No subtype name provided for input buffer passed in -O option
Description
A buffer type of VIEW, X_C_TYPE, X_COMMON, VIEW32, FML or FML32 requires a subtype name to indicate the type of complex data used.
Action
Qualify the type with a subtype using the notation
10
No subtype name provided for input buffer passed in -E option
Description
A buffer type of VIEW, X_C_TYPE, X_COMMON, VIEW32, FML or FML32 requires a subtype name to indicate the type of complex data used.
Action
Qualify the type with a subtype using the notation
10
Bad file or directory: filename
Description
The file or directory listed could not be found or opened.
Action
Ensure that the file or directory exists, and that permissions allow reading.
13
This tool works at the header file level and not for directories like directory
Description
A header file name is expected, but the name given corresponds to a directory.
Action
Ensure that the header file name is that of an actual header file.
14
Could not open file: filename
Description
A header file could not be processed.
Action
Ensure that the file exists, is a valid header file and that file permissions are set correctly.
15
Buffer type type used in -I option incompatible with interface (interface).
Description
The buffer type specified using the -I switch is incompatible with that of the interface.
Action
Ensure that buffer type and interface have consistent buffer types. For instance a C structure cannot be contained in a STRING buffer.
16
Buffer type type used in -O option incompatible with interface (interface).
Description
The buffer type specified using the -O switch is incompatible with that of the interface.
Action
Ensure that buffer type and interface have consistent buffer types. For instance a C structure cannot be contained in a STRING buffer.
17
Class name too long (> 127 characters): name
Description
The class name of the interface being processed is too long.
Action
Please use a class name which lenght is shorter than 128 characters.
18
Invalid service type value: value
Description
An incorrect service type has been specified in the composite file.
Action
Make sure that the /serviceType element is either 'OneWay' or 'RequestResponse'.
19
Could not find service or reference service or reference in composite, componentType, or the interface is invalid
Description
The composite or componentType does not contain the service or reference listed, or the interface file is invalid.
Action
Make sure that the composite or componentType files contain the service or reference mentioned, or that the interface file is valid, i.e. no compiler error is produced when it is used to build the client or server executables.
20
Invalid command line for option option
Description
A syntax error occurred when parsing the command line options.
Action
Check the offending option in the error message and correct it.
21
There was a problem parsing the interface interface
Description
The command could not process the interface.
Action
Ensure that the interface file is valid. For instance, make sure that no compiler error occurs when the interface is compiled when building the client or server executables.
22
There was a problem parsing the interface for service servicename
Description
The command could not process the interface for the service indicated.
Action
Ensure that the interface file is valid. For instance, make sure that no compiler error occurs when the interface is compiled when building the client or server executables.
23
The SCA composite file provided as the -c option cannot be accessed, the option given was: option
Description
The composite file specified using the -c switch could not be opened.
Action
Ensure that the composite file exists, is not a directory, and has correct permission rights.
24
Buffer type type used in -E option incompatible with interface (interface).
Description
The buffer type specified using the -O switch is incompatible with that of the interface.
Action
Ensure that buffer type and interface have consistent buffer types. For instance a C structure cannot be contained in a STRING buffer.
25
FML Field tables location directory is invalid
Description
The FML Field tables location indicated could not be accessed.
Action
Ensure that the FML Field tables location specified is a directory that contains FML Field tables and that its access permissions are correct.
26
FML32 Field tables location directory is invalid
Description
The FML32 Field tables location indicated could not be accessed.
Action
Ensure that the FML32 Field tables location specified is a directory that contains FML Field tables and that its access permissions are correct.
27
FML Field table table does not exist
Description
The FML Field table specified could not be opened.
Action
Ensure that the file exists and has correct access permissions.
28
FML32 Field table table does not exist
Description
The FML32 Field table specified could not be opened.
Action
Ensure that the file exists and has correct access permissions.
29
Composite interface interface is different from componentType interface interface
Description
The composite and componentType interfaces are not consistent.
Action
Ensure that the SCDL code referencing interfaces (composite and componentType files) is consistent.
30
Invalid URL for -a parameter
Description
The URL value used with the -a switch is invalid.
Action
Ensure that the syntax of the URL specified is correct.
 |
 |
 |