IBM WebSphere ILOG JRules connector messages
All the IBM® WebSphere® ILOG® JRules connector messages are listed by the alphanumeric order of the message IDs, and can be searched for by the message IDs.
You must be familiar with the functions of the operating system where the IBM WebSphere ILOG JRules connector is installed. You can use the information in this message reference to identify an error or warning and resolve the problem by using the appropriate recovery action. You can also use this information to understand where the messages are generated and logged.
Each message has a message identifier that consists of a prefix (IIS) and a message number. Messages are listed in numeric sequence based upon the message number. There are three message types: Error, Warning, and Informational. Message identifiers ending with an E are error messages. Those ending with a W indicate warning. Messages ending in an I indicates informational messages.
- IIS-CONN-JRULES-00001E
The connector encountered a record with the error: reject condition on the input link at index link index, and a reject link with that reject condition was not associated with the input link. The input link indexes are zero-based. - IIS-CONN-JRULES-00002E
The connector encountered an error while invoking JRules. The reported error is: error text. - IIS-CONN-JRULES-00003E
The connector was configured for Dynamic XOM and it encountered columns first column and second column that can both be used for the XML data. - IIS-CONN-JRULES-00004E
The connector was configured to propagate unmatched fields with the matching based on the order of records, and the number of records consumed on the input link input link index does not match the number of records produced on the corresponding output link output link index. - IIS-CONN-JRULES-00005E
The connector was configured to propagate unmatched fields with the matching based on input and output Java object identifiers, and the output Java object identifier does not match the identifier of any Java object on input. - IIS-CONN-JRULES-00006E
The connector was configured to propagate unmatched fields with the matching based on key values present in records, and the field propagation key was not defined for any of the input links. The field propagation key must be specified for at least one input link. - IIS-CONN-JRULES-00007E
The connector was configured to propagate unmatched fields with the matching based on key values present in records, and the column column name was included in the field propagation key while at the same time this column is an unmatched column eligible for propagation. This combination is not supported. - IIS-CONN-JRULES-00008E
The connector encountered an error while trying to establish JRules session. The reported error is: error text. - IIS-CONN-JRULES-00009E
The connector encountered an unsupported data type code: data type. - IIS-CONN-JRULES-00010W
The connector encountered an internal error. The argument argument name has the NULL value. - IIS-CONN-JRULES-00011E
The output parameter parameter name was returned by JRules and this output parameter was not specified for any of the output links. - IIS-CONN-JRULES-00012E
The ruleset parameter class was not specified for the input link at index link index. A valid fully-qualified class name must be specified. The input link indexes are zero-based. - IIS-CONN-JRULES-00013E
The ruleset parameter class was not specified for the output link at index link index. A valid fully-qualified class name must be specified. The output link indexes are zero-based. - IIS-CONN-JRULES-00014E
The ruleset parameter name was not specified for the input link at index link index. A valid parameter name must be specified. The input link indexes are zero-based. - IIS-CONN-JRULES-00016E
The connector attempted to assign NULL value to the column column name and this column does not accept NULL values. - IIS-CONN-JRULES-00017E
The connector encountered invalid batch size: batch size. - IIS-CONN-JRULES-00018E
The connector encountered zero batch size but the key processing is enabled and the ruleset contains non-array parameters. The batch size must be greater than zero in this case. - IIS-CONN-JRULES-00019E
The ruleset location value is required but it was not specified. - IIS-CONN-JRULES-00020E
The connector could not load XOM class class name for the input link at index link index. The input link indexes are zero-based. The reported error is: error text. - IIS-CONN-JRULES-00021E
The connector could not load XOM class class name for the output link at index link index. The output link indexes are zero-based. The reported error is: error text. - IIS-CONN-JRULES-00022E
The connector encountered a malformed column description: description text. The expression expression text does not start with CC_JRULES. - IIS-CONN-JRULES-00023E
The connector encountered a malformed column description: description text. The expression expression text does not have an opening parenthesis ( after CC_JRULES. - IIS-CONN-JRULES-00024E
The connector encountered a malformed column description: description text. The expression expression text does not have a closing parenthesis ) at the end. - IIS-CONN-JRULES-00025E
The connector encountered a malformed column description: description text. The description has the trailing text: trailing text after CC_JRULES(). - IIS-CONN-JRULES-00026E
The connector encountered a malformed column description: description text. The expression expression text should be in format: CC_JRULES(method_name,index). - IIS-CONN-JRULES-00027E
The connector encountered a malformed column description: description text. The expression expression text should be in format: CC_JRULES(method_name) - IIS-CONN-JRULES-00028E
The connector encountered a malformed column description: description text. The expression expression text has an empty method name. - IIS-CONN-JRULES-00029E
The connector encountered a malformed column description: description text. The expression expression text does not have an index. The expression should be in format: CC_JRULES(method_name,index). - IIS-CONN-JRULES-00030E
The connector encountered a malformed column description: description text. The expression expression text has a negative index. The expression should be in format: CC_JRULES(method_name,index) and the index value must be a positive integer. - IIS-CONN-JRULES-00031E
The connector encountered a malformed column description: description text. The expression expression text has the index that is not an integer. The expression should be in format: CC_JRULES(method_name,index) and the index value must be a positive integer. - IIS-CONN-JRULES-00032E
The connector encountered a malformed column description: description text. The description for the output column should be in format: CC_JRULES(method_name);. The specified description contains multiple method names for the same column. - IIS-CONN-JRULES-00033E
The connector encountered an error while invoking the method: method name. on the object of Java XOM class: class name. The reported error is: error text. - IIS-CONN-JRULES-00034E
The method name: method name specified in the column description was not found in the XOM class: class name. - IIS-CONN-JRULES-00035E
The connector encountered errors from JRules while parsing the ruleset archive: archive name. The reported errors are: error text. - IIS-CONN-JRULES-00036E
The column description does not have the definition for parameter at index: parameter index for method: method name in XOM class: class name. - IIS-CONN-JRULES-00037E
The data type of the column: column name on input does not match the data type of the field with the same name defined in the XOM object. - IIS-CONN-JRULES-00038E
The data type of the column: column name on output does not match the data type of the field with the same name defined in the XOM object. - IIS-CONN-JRULES-00039E
The method name: column name was detected in the column description as well as in the output XOM class, but the return type of the method defined in the XOM class is not compatible with the data type of the corresponding column on the output link. - IIS-CONN-JRULES-00040E
The method name: column name was detected in the column description as well as in the the input XOM class, and the number of parameters is the same in both places, but the data types of the parameters expected by the method are not compatible with the data types of the corresponding columns on the input link. - IIS-CONN-JRULES-00041E
The key processing was enabled for the stage but no columns were selected for the key. At least one column must be selected. The selected columns must be defined on all input links. - IIS-CONN-JRULES-00042E
The ruleset parameter is based on Java XOM, and two columns: first column name and: second column name are both mapped to it. Only one column can be mapped to the same ruleset parameter. - IIS-CONN-JRULES-00043E
The ruleset parameter is based on Java XOM and no columns are mapped to this parameter. - IIS-CONN-JRULES-00044E
The ruleset parameter is based on Java XOM and a column of the compatible ruleset parameter type that maps to this parameter was not found on the output link. - IIS-CONN-JRULES-00045E
The ruleset parameter is based on Java XOM and a column of the compatible ruleset parameter type that maps to this parameter was not found on the input link. - IIS-CONN-JRULES-00046E
The connector encountered unsupported ruleset parameter data type: class name. - IIS-CONN-JRULES-00047E
Two output columns: first column name and: second column name map to the same ruleset parameter. Exactly one column must be mapped to the ruleset parameter. - IIS-CONN-JRULES-00048E
Two input columns: first column name and second column name map to the same ruleset parameter. Exactly one column must be mapped to the ruleset parameter. - IIS-CONN-JRULES-00049E
The connector was configured for Dynamic XOM but no columns were identified for the XML data. Please identify the column containing the XML document by specifying CC_JRules(); expression in the column description or by ensuring that exactly one column on the link has Char, VarChar, LongVarChar, NChar, NVarChar or LongNVarChar data type. - IIS-CONN-JRULES-00050E
The connector encountered a record with the error: reject condition on the input link at index link index, and a reject link associated with this input link does not have the reject condition reject condition selected. The input link indexes are zero-based. - IIS-CONN-JRULES-00051E
The connector encountered a duplicate field propagation key value: value for the column: column name on the input link at offset: link index during the rule execution cycle. The field propagation key value must be unique within the rule execution cycle. The input link indexes are zero-based. - IIS-CONN-JRULES-00052E
The connector encountered invalid JRules engine mode value: engine mode - IIS-CONN-JRULES-00053E
The connector encountered an invalid XOM type: xom type - IIS-CONN-JRULES-00054E
The ILOG JRules connector has been configured as a target stage. This configuration is not supported by the connector. - IIS-CONN-JRULES-00055E
The ILOG JRules connector has been configured as a source stage. This configuration is not supported by the connector. - IIS-CONN-JRULES-00056E
Field propagation has been enabled using Java object id based mapping. However, none of the output links have a ruleset parameter Java class which maps to any of input input link ruleset parameter. - IIS-CONN-JRULES-00057E
The column column name is a candidate for field propagation on the input link and is also defined on the output link. However the data types do not match and hence data will not be propagated for this column. - IIS-CONN-JRULES-20001W
A request was made to the connector to establish the JRules session, but the session is already established. - IIS-CONN-JRULES-20002W
A request was made to the connector to close the JRules session, but the session was never established or it has already been closed. - IIS-CONN-JRULES-30001I
The connector will enforce the batch of 1 because the ruleset parameter Java type: class name is not an array type and the key processing is not enabled for the stage. - IIS-CONN-JRULES-30002I
The connector will enforce the batch size of 1 because the ruleset parameter Java type: class name specified for the master input link is not of an array type. - IIS-CONN-JRULES-30003I
No records were found on the secondary input link at index link index that match any of the records retrieved on the master input link. - IIS-CONN-JRULES-30004I
CC_JRULES expression was not specified in the description attribute of the input column: column name. - IIS-CONN-JRULES-30005I
CC_JRULES expression was not specified in the description attribute of the output column: column name. - IIS-CONN-JRULES-30006I
The fields: column names in the record have the value: value and the expected value for this field is one of the following: expected values. - IIS-CONN-JRULES-30007I
The link at index link index does not have any more records available that can be combined with the master link record to invoke the ruleset or it is a buffer link that is associated with a ruleset parameter that is not of an array type. The leftover records will be sent to the reject link. - IIS-CONN-JRULES-30008I
The field: column name in the record has the NULL value and the ruleset parameter definition does not accept NULL values for this field. - IIS-CONN-JRULES-30009I
The ruleset at location: ruleset location was successfully loaded and parsed. - IIS-CONN-JRULES-30010I
The connector established a JRules session. - IIS-CONN-JRULES-30011I
The batch processing was enabled for the stage. The batch size is: batch size. - IIS-CONN-JRULES-30012I
The key processing was enabled for the stage. The key columns are: key columns. - IIS-CONN-JRULES-30013I
Number of times the ruleset was invoked on the current node: count - IIS-CONN-JRULES-30014I
The batch processing was disabled and the key processing was enabled for the stage. The connector will automatically run in key mode with the batch size of 0. - IIS-CONN-JRULES-30015I
The batch processing and key processing were disabled for the stage. The connector automatically runs in key mode with the batch size of 1. - IIS-CONN-JRULES-30016I
The connector stage was configured to run in parallel mode on node count nodes. - IIS-CONN-JRULES-30017I
The connector stage was configured to run in sequential mode. - IIS-CONN-JRULES-30018I
The connector will enforce the use of hash partitioner on the current link based on the key columns specified for the stage. - IIS-CONN-JRULES-30019I
The connector will enforce sorting of input records on the current link based on the key columns specified for the stage. - IIS-CONN-JRULES-63300E
The ruleset filter expression was not specified. The wizard requires that a non-empty ruleset filter expression is specified. - IIS-CONN-JRULES-63301E
A source code directory path value must be specified. Specify the full path for an existing directory on the engine tier machine. - IIS-CONN-JRULES-63302E
The specified directory (directory path) does not exist on the engine tier host. Ensure that the directory exists, that it can be written to and that it is a directory and not a file. - IIS-CONN-JRULES-63303E
File file path already exists and selection was made not to overwrite existing files. - IIS-CONN-JRULES-63304E
The code for the Java type class name cannot be generated because no column was found on link link name to match the argument first argument index of the method method name in this Java type. The argument at position first argument index must exist because the argument second argument index exists and is matched by the column column name on the same link. - IIS-CONN-JRULES-63305E
The column column name on link link name specifies argument position argument index in the description expression. The argument positions must be greater than 0 and smaller than maximum index. - IIS-CONN-JRULES-63306E
The column column name on the output link {1} has description expression which includes argument specification (link name). Argument specifications in description expressions are allowed only for input link columns. - IIS-CONN-JRULES-63307E
A member variable prefix value must be specified. - IIS-CONN-JRULES-63308E
The selected ruleset ruleset location has input parameter count input parameter(s), output parameter count output parameter(s) and input/output parameter count input/output parameter(s). Consequently, the stage must have required input link count input link(s) and required output link count output link(s) but it currently has current input link count input link(s) and current output link count output link(s). Select a different ruleset or exit the wizard and define the correct number of links on the stage then repeat the operation. - IIS-CONN-JRULES-63309E
The specified column name column name is invalid. Column names must start with an alphabetic or underscore (_) character and must contain alpha-numeric, underscore (_), dollar ($) and period (.) characters only. - IIS-CONN-JRULES-63310E
The selected archive file path is not a valid ruleset archive. The file descriptor.xml could not be located in the archive. - IIS-CONN-JRULES-63311E
The selected ruleset archive file path could not be parsed. The reported error is: error text - IIS-CONN-JRULES-63312E
A ruleset must be selected. Select the ruleset for which to configure the stage. - IIS-CONN-JRULES-63313E
Multiple rulesets were selected and only one ruleset is allowed to be selected. The wizard automatically preserved the first selected ruleset and cleared the remaining selections. Click Next to proceed with the automatic selection or choose a different ruleset and ensure that it is the only ruleset that was selected. - IIS-CONN-JRULES-63314E
The specified log file file path could not be opened. The error message is: error text - IIS-CONN-JRULES-63315E
One or more Java XOM classes could not be found. The wizard requires access to these classes in order to configure link schema definitions for the stage. Ensure that the classes are included in the classpath and retry the operation. The classes that could not be found are: class names - IIS-CONN-JRULES-63316E
The selected ruleset path ruleset location could not be processed. The reported error is: error text. - IIS-CONN-JRULES-63317E
The JRules management session could not be created. The reported error is: error text. - IIS-CONN-JRULES-63318E
The internal JRules wrapper object could not be accessed. Ensure that the required JRules resources are specified in the class path. The reported error is: error text. - IIS-CONN-JRULES-63319E
The specified filter expression filter expression does not point to an existing directory or file on the engine tier host. Ensure that the full path to an existing directory or file is specified. - IIS-CONN-JRULES-63320E
The specified filter expression filter expression points to a file that is not an archive. When an existing file is specified it must have .jar or .zip extension. - IIS-CONN-JRULES-63321E
The link first link name does not have parameter name specified and the link second link name has parameter name parameter name specified. If one link has parameter name specified, then all links must have the parameter name specified. Ensure that all links specify valid and unique parameter names, or remove the parameter names from all links. - IIS-CONN-JRULES-63322E
The link first link name. and the link second link name both have the direction link direction and they specify the same parameter name parameter name. Links that have the same direction must not specify the same parameter name. - IIS-CONN-JRULES-63323E
The link link name specifies parameter name parameter name which is not found in the ruleset. When parameter names are specified for the links they must match the existing parameter names of the ruleset for which the stage is configured. - IIS-CONN-JRULES-63324E
The link link name specifies parameter name parameter name which is not valid because the direction of the link is link direction and the direction of the parameter is parameter direction. - IIS-CONN-JRULES-63325E
The column name column name is specified more than once. All the column names on the link must be unique. - IIS-CONN-JRULES-65000E
While performing the operation the wizard received the exception exception type with the message: error text.