WebSphere Process Server messages     Operating Systems: All supported
CWLAS0001E: The calling context that was passed into the {0} map is not valid.
Explanation: The relationship transform cannot run without a valid calling context.
User Action: If the transform is invoked manually, please specify a valid calling context as a parameter.

 

CWLAS0002E: The {0} map was not found.
Explanation: The specified map was not found by the map service.
User Action: Make sure that the specified map exists. If it does not exist, please create it.

 

CWLAS0003E: The execution of the {0} map failed because of the exception: {1}.
Explanation: The exception has provides a detailed explanation of the problem.
User Action: Based on the exception details, make sure that the map is in the proper format and that it has compiled successfully.

 

CWLAS0004E: The calling context in the {0} map is null.
Explanation: The relationship transform cannot run without a valid calling context.
User Action: If the transform is invoked manually, please specify a valid calling context as a parameter.

 

CWLAS0005E: The data of the {0} type cannot be converted to data of the {1} type.
Explanation: The conversion between the types is not supported by the map service, or the values of the data types contain errors.
User Action: Verify that the conversion is supported by the map service and that the values are valid.

 

CWLAS0006E: The data of the {0} type with the {1} value cannot be converted to data of the {2} type.
Explanation: The conversion between the specified types is not supported by the map service, or the data contains errors.
User Action: Verify that the conversion is supported by the map service and that the data is correct.

 

CWLAS0007E: No element was found at the {0} position. The maximum position index is {1}.
Explanation: The specified position index is not in the range of the maximum position index, or the value of the index is not valid.
User Action: Verify that the element exists at the specified position. If the element is in the correct position, change the index to the value where the element exists.

 

CWLAS0008E: The {0} method does not support {1} data type for the input argument at the position {2}.
Explanation: For the method DtpUtils.truncate, the supported data types for the input argument are string, float, and double.
User Action: Specify the correct data type and input argument for the method.

 

CWLAS0009E: The {0} attribute does not exist in the {1} business object.
Explanation: If an attribute is specified in a business object, then it must exist in that business object.
User Action: Add the specified attribute to the business object or change the attribute to an existing one.

 

CWLAS0010E: The subscript {0}, which is specified for the {1} attribute in the {2} business object, is not valid.
Explanation: A valid subscript value must correspond to the index position of the specified attribute, and it must be less than the total size. If the attribute is a single-cardinality child in the business object, then a subscript is not required. However, if the attribute is a multiple-cardinality child, then a subscript is required.
User Action: Specify a valid subscript for the attribute in the business object.

 

CWLAS0011E: The {0} attribute of the {1} data type in the {2} business object is not valid. It is specified as {3} of the {4} transform.
Explanation: The transform was unsuccessful because of one of the following reasons: 1) The target of a Join transform is not of the data type string. 2) The source of an Extract transform is not of the data type string. 3) The automatic type conversion of a move transform failed because of an unacceptable conversion from boolean to anything except string, or vice versa.
User Action: Specify a valid attribute for the business object in the Business Object Editor.

 

CWLAS0012E: The following runtime validation error has occurred: {0}
Explanation: A runtime validation error is returned when the instance data that is passed into the map run time is not valid, is null, or is inconsistent with the schema of the data that is specified in the map definition during design.
User Action: Verify that the instance data for the inputs and the outputs is consistent with the map definition.

 

CWLAS0013E: No subscript is specified for the {1} attribute in the {2} business object.
Explanation: A subscript is required for the specified attribute.
User Action: Specify the subscript for the specified attribute in the Business Object Editor.

 

CWLAS0014E: The {0} date format is not valid.
Explanation: The correct date format is YYYY-MM-DDThh:mm:ss.sZ
User Action: Specify the correct format for the date.

 

CWLAS0015E: The {0} transform #{1} in the {2} map did not complete because of the following exception: {3}
Explanation: This error is likely to occur when the transform inputs and outputs are inconsistent with the map definition. A more detailed cause of the exception is captured in the specified exception message.
User Action: Verify that inputs and outputs are not null and are consistent with the map definition.

 

CWLAS0016E: The input object with the {0} variable name in the {1} map is null.
Explanation: The input object passed into the map cannot be null.
User Action: Make sure the input object that is passed into the map is not null.

 

CWLAS0017E: The output object with the {0} variable name in the {1} map is null.
Explanation: The output object passed into the map cannot be null.
User Action: Make sure the output object that is passed into the map is not null.

 

CWLAS0018E: Input/output parameters of the Relationship transform are not valid.
Explanation: Either the input or the output parameters of the Relationship transform is null.
User Action: Make sure input/output parameters of the Relationship transform are specified properly.

 

CWLAS0019E: The input/output parameters of the submap transform are not valid.
Explanation: If the submap has one input of multiple cardinality, then each of the multiple outputs must be of single cardinality.
User Action: Make sure input/output parameters of the submap transform are specified properly in the Business Object Mapping Editor.

 

CWLAS0020E: The index {0} specified on the {1} attribute is ambiguous.
Explanation: The index cannot be resolved, because instances for it exist both in the graph and in the change summary.
User Action: Ensure all business objects reside either in the graph or in the change summary when invoking this transform.

 

CWLAS0021E: A simple type is mapped to the {0} complex type.
Explanation: A complex type is not compatible with a simple type so they cannot be mapped.
User Action: Verify that the input and output properties are compatible.

 

CWLAS0022E: The {0} complex type is mapped to a simple type.
Explanation: A complex type is not compatible with a simple type so they cannot be mapped.
User Action: Verify that the input and output properties are compatible.

 

CWLAS0023E: The submap {0} is not valid because a simple type is being mapped as part of the submap transform.
Explanation: A submap transform cannot have a simple type as its Input or Output.The Input and Output must be Business Objects.
User Action: To create a submap transform between AnyType or xsd:any, the input and output types must contain Business Objects.

 

CWLAS0024E: The value of the {0} intermediate business object in the {1} property path is null or invalid.
Explanation: In order for a property to exist at a specific path, intermediate business objects preceeding the property must exist.
User Action: Verify that the property exists before invoking a transform with it.

 

CWLAS0025E: The {0} property of the {1} business object must be a string data type.
Explanation: Only string data types are valid for the input of an Extract transform.
User Action: Verify that the input of the Extract transform is a string data type.

 

CWLAS0026E: The {0} property of the {1} business object is not a string data type.
Explanation: Only string data types are valid for the output of a Join transform.
User Action: Verify that the output of the Join transform is a string data type.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009