6.6-dm_expression

DM_EXPRESSION


ERROR: [DM_EXPRESSION_F_FUNC_EXPR_TYPE_INIT]

SEVERITY: FATAL

DESCRIPTION: S Failed to initialize type %s.

CAUSE: Unknown.

ACTION: Report this message and any parameters to your Documentum site representative.

PARAMS:

 

ERROR: [DM_EXPRESSION_F_EXPRESSION_MANAGER_INTERNAL]

SEVERITY: FATAL

DESCRIPTION: S Internal error (%s) in the Expression Manager.

CAUSE: This is an internal error.

ACTION: Report this error to Documentum sysadmins.

PARAMS: The first parameter is the internal error message.

 

ERROR: [DM_EXPRESSION_F_COND_ID_EXPR_TYPE_INIT]

SEVERITY: FATAL

DESCRIPTION: S Failed to initialize type %s.

CAUSE: Unknown.

ACTION: Report this message and any parameters to your Documentum site representative.

PARAMS:

 

ERROR: [DM_EXPRESSION_F_LITERAL_EXPR_TYPE_INIT]

SEVERITY: FATAL

DESCRIPTION: S Failed to initialize type %s.

CAUSE: Unknown.

ACTION: Report this message and any parameters to your Documentum site representative.

PARAMS:

 

ERROR: [DM_EXPRESSION_F_CANNOT_CLONE_EXPRESSION]

SEVERITY: FATAL

DESCRIPTION: D Cannot clone expression object with ID %s.

CAUSE: This is an internal error.

ACTION: Report this error to Documentum sysadmins.

PARAMS: The parameter is the object id of the expression object.

 

ERROR: [DM_EXPRESSION_F_COND_EXPR_BAD_VSTAMP]

SEVERITY: FATAL

DESCRIPTION: II Type dm_cond_expr has a bad vstamp %d. The current vstamp for dm_cond_expr is supposed to be %d.

CAUSE: The RDBMS table has a bad vstamp.

ACTION: Report this error to Documentum sysadmins.

PARAMS:

 

ERROR: [DM_EXPRESSION_F_LITERAL_EXPR_BAD_VSTAMP]

SEVERITY: FATAL

DESCRIPTION: II Type dm_literal_expr has a bad vstamp %d. The current vstamp for dm_literal_expr is supposed to be %d.

CAUSE: The RDBMS table has a bad vstamp.

ACTION: Report this error to Documentum sysadmins.

PARAMS:

 

ERROR: [DM_EXPRESSION_F_FUNC_EXPR_BAD_VSTAMP]

SEVERITY: FATAL

DESCRIPTION: II Type dm_func_expr has a bad vstamp %d. The current vstamp for dm_func_expr is supposed to be %d.

CAUSE: The RDBMS table has a bad vstamp.

ACTION: Report this error to Documentum sysadmins.

PARAMS:

 

ERROR: [DM_EXPRESSION_F_EXPRESSION_TYPE_INIT]

SEVERITY: FATAL

DESCRIPTION: S Failed to initialize type %s.

CAUSE: Unknown.

ACTION: Report this message and any parameters to your Documentum site representative.

PARAMS:

 

ERROR: [DM_EXPRESSION_F_BUILTIN_EXPR_TYPE_INIT]

SEVERITY: FATAL

DESCRIPTION: S Failed to initialize type %s.

CAUSE: Unknown.

ACTION: Report this message and any parameters to your Documentum site representative.

PARAMS:

 

ERROR: [DM_EXPRESSION_F_NULL_CODE_OBJECT_ID_FOR_FUNC_EXPR]

SEVERITY: FATAL

DESCRIPTION: D A NULL object id was given for the code object for the dm_expression object with id %s.

CAUSE: This is an internal error.

ACTION: Report this error to Documentum sysadmins.

PARAMS: The parameter is the object id of the expression object. $Id: dmfilter.e,v 5.0 1998/01/10 02:07:42 sol_ora Exp $ Filter class errors

 

ERROR: [DM_EXPRESSION_F_COND_EXPR_TYPE_INIT]

SEVERITY: FATAL

DESCRIPTION: S Failed to initialize type %s.

CAUSE: Unknown.

ACTION: Report this message and any parameters to your Documentum site representative.

PARAMS:

 

ERROR: [DM_EXPRESSION_F_EXPRESSION_BAD_VSTAMP]

SEVERITY: FATAL

DESCRIPTION: II Type dm_expression has a bad vstamp %d. The current vstamp for dm_expression is supposed to be %d.

CAUSE: The RDBMS table has a bad vstamp.

ACTION: Report this error to Documentum sysadmins.

PARAMS:

 

ERROR: [DM_EXPRESSION_F_BUILTIN_EXPR_BAD_VSTAMP]

SEVERITY: FATAL

DESCRIPTION: II Type dm_builtin_expr has a bad vstamp %d. The current vstamp for dm_builtin_expr is supposed to be %d.

CAUSE: The RDBMS table has a bad vstamp.

ACTION: Report this error to Documentum sysadmins.

PARAMS:

 

ERROR: [DM_EXPRESSION_F_PARSER_INTERNAL_AT]

SEVERITY: FATAL

DESCRIPTION: SII Internal error (%s) at line %d, column %d of expression.

CAUSE: This is an internal error.

ACTION: Report this error to Documentum sysadmins.

PARAMS: The first parameter is the internal error message. The second parameter is the line number within the expression. The third parameter is the column number within the line.

 

ERROR: [DM_EXPRESSION_F_EXPRESSION_CANT_EXPUNGE]

SEVERITY: FATAL

DESCRIPTION: D Cannot expunge expression object with ID %s.

CAUSE: This is an internal error.

ACTION: Report this error to Documentum sysadmins.

PARAMS: The parameter is the object id of the expression object.

 

ERROR: [DM_EXPRESSION_F_COND_ID_EXPR_BAD_VSTAMP]

SEVERITY: FATAL

DESCRIPTION: II Type dm_cond_id_expr has a bad vstamp %d. The current vstamp for dm_cond_id_expr is supposed to be %d.

CAUSE: The RDBMS table has a bad vstamp.

ACTION: Report this error to Documentum sysadmins.

PARAMS:

 

ERROR: [DM_EXPRESSION_E_COMPILATION]

SEVERITY: ERROR

DESCRIPTION: IIS The expression compilation attempt failed. Error Number is %d, Error Line is %d and Error Text is %s.

CAUSE: The expression compilation attempt failed.

ACTION: Correct the expression errors and retry compilation.

PARAMS: The first parameter is the error number. The second parameter is the error line. The third parameter is the error text.

 

ERROR: [DM_EXPRESSION_E_DOCBASIC_UNEXPECTED_RETURN_TYPE]

SEVERITY: ERROR

DESCRIPTION: I The Docbasic Engine has reported a return type of %d that is different than what is expected for the expression.

CAUSE: The resulting return value from executing a docbasic expression is not what was expected.

ACTION: Verify that the expression_text actually evaluates to the appropriate return data type.

PARAMS: The data type of the return value – mapped to the docbasic engines data type definitions.

 

ERROR: [DM_EXPRESSION_E_DOCBASIC_ENGINE]

SEVERITY: ERROR

DESCRIPTION: II An error has occurred in the docbasic engine in mode %d of type %d.

CAUSE: The docbasic engine has reported an engine error. Most likely this is a memory allocation issue. ACTION:Call Documentum Tech Support for assistence.

ACTION:

PARAMS: integer representation of the error mode and type.

 

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_INVALID_ROUTINE_ID]

SEVERITY: ERROR

DESCRIPTION: The attribute routine_id is not a valid object id.

CAUSE: The routine_id does not reference a valid sysobject.

ACTION: Use a valid sysobject id.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_PARSER_MALFORMED_NUMBER_AT]

SEVERITY: ERROR

DESCRIPTION: II Malformed numeric literal at line %d, column %d.

CAUSE: The expression contains an illegal numeric literal.

ACTION: Correct the numeric literal at the indicated location.

PARAMS: The first parameter is the line number within the expression. The second parameter is the column number within the line.

 

ERROR: [DM_EXPRESSION_E_UNABLE_TO_COMPILE]

SEVERITY: ERROR

DESCRIPTION: DDI The Expression Manager encountered a compilation error for expression with id %s. Check the source code stored in routine id %s, page %d.

CAUSE: The expression compilation attempt failed.

ACTION: Look at the source code for the expression to try and understand the compilation error information.

PARAMS: The first parameter is the object id of the expression object. The second parameter is the object id of the sysobject that contains the source code. The third parameter is the source page where the source code is located.

 

ERROR: [DM_EXPRESSION_E_EXECUTION_INVALID_OBJECT_ID]

SEVERITY: ERROR

DESCRIPTION: SSI The Expression Manager found an invalid object_id of %s of type %s at position %d.

CAUSE: An invalid object id has been specified during expression evaluation.

ACTION: Verify that the object id that is being supplied for expression execution is valid.

PARAMS: The first parameter is the invalid object id (in string form) that was supplied. The second parameter is the type that the object id is supposed to correspond to. The third parameter is the position of the object id in the object list.

 

ERROR: [DM_EXPRESSION_E_INVALID_DATA_TYPE]

SEVERITY: ERROR

DESCRIPTION: I An invalid data type %d has been specified.

CAUSE: An invalid data type has been specified.

ACTION: Make sure that only valid data types are being used.

PARAMS: The integer representation of the data type – maps to dmPrimitives.

 

ERROR: [DM_EXPRESSION_E_BUILTIN_EXPR_CANT_FETCH]

SEVERITY: ERROR

DESCRIPTION: D Cannot fetch – Invalid object ID %s.

CAUSE: Could not fetch an object with the given id.

ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.

PARAMS:

 

ERROR: [DM_EXPRESSION_E_PARSER_UNEXPECTED_CHAR_AT]

SEVERITY: ERROR

DESCRIPTION: SII Unexpected character (%s) at line %d, column %d of expression.

CAUSE: The expression string contains an illegal character.

ACTION: Remove the illegal character at the indicated location.

PARAMS: The first parameter is the illegal character. The second parameter is the line number within the expression. The third parameter is the column number within the line.

 

ERROR: [DM_EXPRESSION_E_COND_EXPR_INVALID_SUBEXPR_ID]

SEVERITY: ERROR

DESCRIPTION: D Invalid Subexpression id %s in expression_list.

CAUSE: The subexpression id does not reference a valid dm_func_expr object

ACTION: Use a valid subexpression id in the expression list.

PARAMS: Invalid ID

 

ERROR: [DM_EXPRESSION_E_GENERATED_SOURCE_FILE_IO]

SEVERITY: ERROR

DESCRIPTION: DS The following IO Error occurred while accessing the source code for expression %s: %s.

CAUSE: An error occured during IO on the generated expression source file.

ACTION: Check the error string to determine an appropriate action.

PARAMS: The first parameter is the id of the expression object. The second parameter is the IO Error reported by the operating system.

 

ERROR: [DM_EXPRESSION_E_EXECUTION_UNABLE_TO_RETRIEVE_STORE_INFO]

SEVERITY: ERROR

DESCRIPTION: DS The Expression Manager was unable to retrieve store information for store %s with name %s.

CAUSE: The Expression Manager was not able to retrieve information from the store needed for pcode execution.

ACTION: Check that the storage object is valid.

PARAMS: The first parameter is the object id of the storage object. The second parameter is the name of the store.

 

ERROR: [DM_EXPRESSION_E_EXECUTION_UNABLE_TO_RETRIEVE_PCODE]

SEVERITY: ERROR

DESCRIPTION: DD The Expression Manager was unable to retrieve pcode for expression with id %s which is stored in sysobject with it %s.

CAUSE: The Expression Manager was not able to retrieve pcode from the sysobject specified by routine_id attribute of the expression object.

ACTION: Verify that the sysobject exists and that the pcode is indeed stored there.

PARAMS: The first parameter is the object id of the expression object. The second parameters is the object id of the sysobject pointed to by routine_id.

 

ERROR: [DM_EXPRESSION_E_SOURCE_PAGE_MISMATCH]

SEVERITY: ERROR

DESCRIPTION: SS Expression objects must have the same source_pages in order for source code to be stored together. The expression object with object ids %s and %s have different source_pages. CAUSE:An attempt has been made to store source code for multiple expression together, but the expressions have different source_pages.

CAUSE:

ACTION: Make sure that expressions that are going to have source code stored together have the same source_pages.

PARAMS: The first parameter is the object id of the first expression object. The second parameter is the object id of the second expression object.

 

ERROR: [DM_EXPRESSION_E_ROUTINE_ID_MISMATCH]

SEVERITY: ERROR

DESCRIPTION: SS Expression objects must have the same routine_ids in order for source code to be stored together. The expression objects with object ids %s and %s have different routine_ids.

CAUSE: An attempt has been made to store source code for multiple expression together, but the expressions have different routine_ids.

ACTION: Make sure that expressions that are going to have source code stored together have the same routine_ids.

PARAMS: The first parameter is the object id of the first expression object. The second parameter is the object id of the second expression object.

 

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_INVALID_SOURCE_PAGE]

SEVERITY: ERROR

DESCRIPTION: The attribute source_page must be 0.

CAUSE: The source page must be 0 for Piper.

ACTION: Make sure the source page is set to 0.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_INCREASE_LENGTH]

SEVERITY: ERROR

DESCRIPTION: SII Failed to increase the size of %s from %d to %d. PARAMTERS: S – attribute name I – original size of the attribute I – new size of the attribute

CAUSE: For an unknown reason, type conversion failed.

ACTION: Check if there are any database errors or problems. Report the problem to Documentum Support.

PARAMS:

 

ERROR: [DM_EXPRESSION_E_PARSER_UNKNOWN_IDENTIFIER_AT]

SEVERITY: ERROR

DESCRIPTION: SII The parser encountered an unknown identifier %s at line %d, column %d is illegal.

CAUSE: The expression contains an unknown identifier.

ACTION: Correct the identifier in the expression at the indicated location.

PARAMS: The first parameter is the unknown identifier. The second parameter is the line number within the expression. The third parameter is the column number within the line.

 

ERROR: [DM_EXPRESSION_E_UNABLE_TO_EXECUTE]

SEVERITY: ERROR

DESCRIPTION: DDI The Expression Manager encountered an execution error for expression with id %s. Check the source code stored in routine id %s, page %d.

CAUSE: The expression execution attempt failed.

ACTION: Look at the source code for the expression to try and understand the execution error information.

PARAMS: The first parameter is the object id of the expression object. The second parameter is the object id of the sysobject that contains the source code. The third parameter is the source page where the source code is located.

 

ERROR: [DM_EXPRESSION_E_PARSER_SYNTAX_EXPECTED_AT]

SEVERITY: ERROR

DESCRIPTION: SSII Expected %s, found %s at line %d, column %d.

CAUSE: The expression contains a syntax error.

ACTION: Correct the expression to use legal syntax.

PARAMS: The first parameter is the expected token. The second parameter is the actual token found. The third parameter is the line number within the expression. The fourth parameter is the column number within the line.

 

ERROR: [DM_EXPRESSION_E_COMPILATION_UNABLE_TO_RETRIEVE_SOURCE_CODE]

SEVERITY: ERROR

DESCRIPTION: DD The Expression Manager was unable to retrieve the source code for expression %s from sysobject %s.

CAUSE: The Expression Manager was not able to retrieve the source code from the sysobject pointed to by routine_id.

ACTION: Verify that the sysobject pointed to by routine_id is valid and that the source code is stored there.

PARAMS: The first parameter is the object id of the expression object. The second parameter is the object id of the sysobject that is supposed to hold the source code.

 

ERROR: [DM_EXPRESSION_E_SUBSCRIPT_BAD_OPERATOR_AT]

SEVERITY: ERROR

DESCRIPTION: SII The array subscript operation %s at line %d, column %d is illegal.

CAUSE: The expression contains an illegal array operation. Repeating attribute comparisons can only use (>,<,,=,=)

ACTION: Use a valid operator for array comparisons.

PARAMS: The first parameter is the invalid operator that was used. The second parameter is the line number within the expression. The third parameter is the column number within the line.

 

ERROR: [DM_EXPRESSION_E_COND_EXPR_LANGUAGE_MISMATCH]

SEVERITY: ERROR

DESCRIPTION: The cond_expr contains a subexpression that is in a different expression language.

CAUSE: All subexpressions must be in the same expression language.

ACTION: Only add subexpressions of the same language.

PARAMS:

 

ERROR: [DM_EXPRESSION_E_INVALID_EXPRESSION_TYPE]

SEVERITY: ERROR

DESCRIPTION: The expression_type for a dm_expression is invalid.

CAUSE: An attempt was made to create a dm_expression with an invalid expression_type attribute.

ACTION: Supply an expression_type of DM_BOOLEAN for dm_func_expr, DM_INTEGER for dm_cond_expr, or DM_STRING for dm_cond_id_expr.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_INVALID_ALIAS_INFO]

SEVERITY: ERROR

DESCRIPTION: The object_alias information is not complete.

CAUSE: An attempt was made to create a dm_func_expr with an incomplete object_alias list.

ACTION: Make sure each type_name entry has a corresponding object_alias entry.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_CANT_FETCH]

SEVERITY: ERROR

DESCRIPTION: D Cannot fetch – Invalid object ID %s.

CAUSE: Could not fetch an object with the given id.

ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.

PARAMS:

 

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_INVALID_CODE_PAGE]

SEVERITY: ERROR

DESCRIPTION: The attribute code_page must be 1.

CAUSE: The code page must be 1 for Piper.

ACTION: Make sure the code page is set to 1.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_COMPILATION_UNABLE_TO_STORE_PCODE]

SEVERITY: ERROR

DESCRIPTION: DD The Expression Manager was unable to store the pcode for expression object %s in sysobject with id %s.

CAUSE: The Expression Manager encountered an error trying to store pcode for an expression.

ACTION: Verify that the sysobject exists.

PARAMS: The first parameter is the object id of the expression object. The second parameters is the object id of the sysobject pointed to by routine_id.

 

ERROR: [DM_EXPRESSION_E_EXECUTION_OBJECT_ID_MISMATCH]

SEVERITY: ERROR

DESCRIPTION: II The Expression Manager expected %d object ids but was given %d object_ids.

CAUSE: An invalid number of object ids was supplied to the expression manager during execution.

ACTION: Make sure the correct number of object ids are being passed for expression execution.

PARAMS: The first parameter is the number of expected object ids. The second parameter is the number of object ids passed for execution.

 

ERROR: [DM_EXPRESSION_E_PARSER_TOKEN_TOO_LONG_AT]

SEVERITY: ERROR

DESCRIPTION: III The token at line %d, column %d exceeds the maximum token length of %d.

CAUSE: The expression contains a token that is too long.

ACTION: Correct the token to be within the limit given.

PARAMS: The first parameter is the line number within the expression. The second parameter is the column number within the line. The third parameter is the maximum allowed token length.

 

ERROR: [DM_EXPRESSION_E_UNABLE_TO_FETCH_ATTRIBUTE_VALUE]

SEVERITY: ERROR

DESCRIPTION: SSIS The Expression Handler was unable to fetch attribute %s of type %s at index %d for object %s.

CAUSE: The Expression Handler was unable to fetch a value of an attribute for a specified object.

ACTION: Verify that the object ids given to the expression handler are valid.

PARAMS: Attribute, Type, Index, Object ID

 

ERROR: [DM_EXPRESSION_E_COND_ID_EXPR_INVALID_ID_LIST]

SEVERITY: ERROR

DESCRIPTION: The expression_list and id_list attributes are not in synch.

CAUSE: Each expression_list entry must have a corresponding id_list entry.

ACTION: Make sure each expression_list entry has a id_list entry.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_COND_ID_EXPR_MISSING_DEFAULT_ID]

SEVERITY: ERROR

DESCRIPTION: The default_id attribute must be set.

CAUSE: The default_id attribute is not set.

ACTION: Set the default id.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_PARSER_MALFORMED_STRING_AT]

SEVERITY: ERROR

DESCRIPTION: II Malformed string literal at line %d, column %d.

CAUSE: The expression contains an illegal string literal.

ACTION: Correct the string literal at the indicated location.

PARAMS: The first parameter is the line number within the expression. The second parameter is the column number within the line.

 

ERROR: [DM_EXPRESSION_E_CODE_PAGE_MISMATCH]

SEVERITY: ERROR

DESCRIPTION: SS Expression objects must have the same code_pages in order for source code to be stored together. The expression object with object ids %s and %s have different code_pages. CAUSE:An attempt has been made to store source code for multiple expression together, but the expressions have different code_pages.

CAUSE:

ACTION: Make sure that expressions that are going to have source code stored together have the same code_pages.

PARAMS: The first parameter is the object id of the first expression object. The second parameter is the object id of the second expression object.

 

ERROR: [DM_EXPRESSION_E_PARSER_MALFORMED_DATE_AT]

SEVERITY: ERROR

DESCRIPTION: II Malformed date literal at line %d, column %d.

CAUSE: The expression contains an illegal date literal.

ACTION: Correct the date literal at the indicated location.

PARAMS: The first parameter is the line number within the expression. The second parameter is the column number within the line.

 

ERROR: [DM_EXPRESSION_E_INVALID_ATTRIBUTE_INDEX]

SEVERITY: ERROR

DESCRIPTION: SSI The attribute %s of type %s references an invalid index %d.

CAUSE: An invalid index has been specified for the attribute.

ACTION: Check the index and make sure it is valid.

PARAMS: type_name, attribute_name, index

 

ERROR: [DM_EXPRESSION_E_INVALID_EXPRESSION_SYNTAX]

SEVERITY: ERROR

DESCRIPTION: The syntax of the expression_text attribute is invalid.

CAUSE: There is a syntax error in the expression text attribute.

ACTION: Fix the syntax error in the expression.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_INVALID_EXPRESSION_OBJECT]

SEVERITY: ERROR

DESCRIPTION: An invalid operation on an expression object was attempted.

CAUSE: The expression manager cannot perform certain operations on certain forms of expressions. (i.e. dm_func_expr, dm_cond_expr, dm_cond_id_expr)

ACTION: Make sure that the desired operation is indeed valid for the expression object being used.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_USER_FUNCTION_NULL_ROUTINE_NAME]

SEVERITY: ERROR

DESCRIPTION: The routine name for a user function must be set.

CAUSE: A dm_func_expr object of kind DM_EXPR_USER_FUNCTION must have the routine_name attribute set.

ACTION: Make sure a valid routine_name has been specified for the expression.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_INVALID_EXPRESSION_KIND]

SEVERITY: ERROR

DESCRIPTION: The expression_kind for a dm_func_expr must be DM_EXPR_NORMAL or DM_EXPR_USER_ROUTINE.

CAUSE: An attempt was made to create a dm_func_expr with an invalid expression_kind.

ACTION: Supply an expression_kind of DM_EXPR_NORMAL or DM_EXPR_USER_ROUTINE

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_INVALID_ATTRIBUTE_INFO]

SEVERITY: ERROR

DESCRIPTION: The attribute information could not be validated.

CAUSE: Either an attribute_name, type_name, repeat_index or attr_object_index entry is invalid.

ACTION: Make sure attribute information is correct and that indices are valid.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_NULL_TEXT]

SEVERITY: ERROR

DESCRIPTION: The expression_text for a dm_expression cannot be empty.

CAUSE: An attempt was made to create a dm_expression with an empty expression_text attribute.

ACTION: Supply expression_text when creating a dm_expression.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_INVALID_ATTRIBUTE]

SEVERITY: ERROR

DESCRIPTION: SSI The attribute %s of type %s at index %d is invalid.

CAUSE: An invalid attribute was referenced by an expression.

ACTION: Make sure that the attribute referenced is valid for the associated type.

PARAMS: attribute_name

 

ERROR: [DM_EXPRESSION_E_LITERAL_EXPR_CANT_FETCH]

SEVERITY: ERROR

DESCRIPTION: D Cannot fetch – Invalid object ID %s.

CAUSE: Could not fetch an object with the given id.

ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.

PARAMS:

 

ERROR: [DM_EXPRESSION_E_COND_ID_EXPR_CANT_FETCH]

SEVERITY: ERROR

DESCRIPTION: D Cannot fetch – Invalid object ID %s.

CAUSE: Could not fetch an object with the given id.

ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.

PARAMS:

 

ERROR: [DM_EXPRESSION_E_PARSER_ILLEGAL_SUBSCRIPT_AT]

SEVERITY: ERROR

DESCRIPTION: II The array subscript operation at line %d, column %d is illegal.

CAUSE: The expression contains an illegal array subscript operation.

ACTION: Correct the subscript operation at the indicated location.

PARAMS: The first parameter is the line number within the expression. The second parameter is the column number within the line.

 

ERROR: [DM_EXPRESSION_E_INVALID_TYPE]

SEVERITY: ERROR

DESCRIPTION: S The type %s is an invalid type.

CAUSE: An invalid type was referenced by an expression.

ACTION: Make sure that the type referenced does exist.

PARAMS: type_name

 

ERROR: [DM_EXPRESSION_E_COND_EXPR_CANT_FETCH]

SEVERITY: ERROR

DESCRIPTION: D Cannot fetch – Invalid object ID %s.

CAUSE: Could not fetch an object with the given id.

ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.

PARAMS:

 

ERROR: [DM_EXPRESSION_E_UNKNOWN_ERROR]

SEVERITY: ERROR

DESCRIPTION: I An unknown error with code %d has occurred within the expression manager.

CAUSE: An error has occurred within the expression manager and the error code has no mapping.

ACTION: This is an internal error that should not happen, but if it does, please report it.

PARAMS: error_code.

 

ERROR: [DM_EXPRESSION_E_COND_EXPR_INVALID_SUBEXPR_KIND]

SEVERITY: ERROR

DESCRIPTION: Subexpressions cannot be User Routines.

CAUSE: The subexpression is a User Routine.

ACTION: Make sure you do not use User Routines as subexpressions.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_RUNTIME]

SEVERITY: ERROR

DESCRIPTION: IIS The expression execution attempt failed. Error Number is %d, Error Line is %d and Error Text is %s.

CAUSE: The expression execution attempt failed.

ACTION: Correct the expression errors and retry execution.

PARAMS: The first parameter is the error number. The second parameter is the error line. The third parameter is the error text.

 

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_MISSING_TYPE_NAME_INFO]

SEVERITY: ERROR

DESCRIPTION: The type_name attribute must have at least one type specified.

CAUSE: An attempt was made to create a dm_func_expr without a type_name entry.

ACTION: Specify at least one type for the dm_func_expr object.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_INVALID_EXPRESSION_LANG]

SEVERITY: ERROR

DESCRIPTION: The expression_lang for a dm_func_expr must be DM_EXPR_LANG_DOCBASIC.

CAUSE: An attempt was made to create a dm_func_expr with an invalid expression_lang attribute.

ACTION: Supply an expression_lang of DM_EXPR_LANG_DOCBASIC.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_EXPRESSION_CANT_FETCH]

SEVERITY: ERROR

DESCRIPTION: D Cannot fetch – Invalid object ID %s.

CAUSE: Could not fetch an object with the given id.

ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.

PARAMS:

 

ERROR: [DM_EXPRESSION_E_CANNOT_GENERATE_USER_ROUTINES]

SEVERITY: ERROR

DESCRIPTION: Cannot generate a User Routine.

CAUSE: Only Expressions can be generated.

ACTION: Dont generate User Routines.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_E_COND_EXPR_INVALID_SUBEXPRESSION]

SEVERITY: ERROR

DESCRIPTION: The subexpression of the conditional expression object is invalid.

CAUSE: There is some inconsistency between the parent expression object and the subexpression

ACTION: Verify that the subexpression is consistent with the parent expression object.

PARAMS: None.

 

ERROR: [DM_EXPRESSION_W_EXECUTION_PCODE_MISSING]

SEVERITY: WARNING

DESCRIPTION: DDI Expression Manager could not find the pcode for expression with ID %s. The pcode should be stored in the sysobject with ID %s at page %d

CAUSE: The pcode file for the expression was either missing or out of synch with the source code. This suggests that the source code has been manually changed and the corresponding pcode was not regenerated or the pcode was actually deleted.

ACTION: Although expression execution should have completed successfully, it is costly from a performance standpoint to cause the expression manager to recompile the source code each time it is executed. We recommend that you regenerate the expression pcode and store it in the expression sysobject pointed to by the routine_id attribute of the expression object.

PARAMS:

 

ERROR: [DM_EXPRESSION_W_EXPUNGE_COND_ID_EXPR_CANT_FETCH]

SEVERITY: WARNING

DESCRIPTION: D Could not fetch the dm_cond_id_expr object with ID %s during an expunge operation.

CAUSE: Could not fetch an object with the given id.

ACTION: None necessary, the expunge operation continued.

PARAMS: The parameter is the object id.

 

ERROR: [DM_EXPRESSION_W_EXPUNGE_EXPRESSION_CANT_FETCH]

SEVERITY: WARNING

DESCRIPTION: D Could not fetch the expression object with ID %s during an expunge operation.

CAUSE: Could not fetch an object with the given id.

ACTION: None necessary, the expunge operation continued.

PARAMS: The parameter is the object id.

 

ERROR: [DM_EXPRESSION_W_COMPILATION_UNABLE_TO_REMOVE_TEMP_FILE]

SEVERITY: WARNING

DESCRIPTION: DSS The Expression Manager was unable to remove a temporary file used during the compilation of expression with id %s. Removal of the temporary file %s failed due to IO Error: %s.

CAUSE: The Expression Manager was not able to remove a temporary file created during expression compilation.

ACTION: Manually delete the specified temporary file.

PARAMS: The first parameter is the object id of the expression object that was being compiled. The second parameter is the name of the temporary file which could not be removed. The third parameter is the IO Error reported by the operating system.

 

ERROR: [DM_EXPRESSION_W_UNABLE_TO_REMOVE_PCODE_FILE]

SEVERITY: WARNING

DESCRIPTION: DDI The Docbasic Engine was unable to remove the pcode file for expression with id %s after generating new source code. The pcode is stored in sysobject %s at page %d. It should be removed prior to evaluating the expression.

CAUSE: The expression handler was not able to delete the pcode rendition stored in the sysobject.

ACTION: As long as the expression is compiled prior to execution there should be no problem. The only danger is that if you dont compile the expression, the pcode and source could be out of synch.

PARAMS: The first parameter is the object id of the expression object. The second parameter is the object id of the sysobject where the pcode is stored. The third parameter is the page at which the pcode is stored.

 

ERROR: [DM_EXPRESSION_W_GENERATION_UNABLE_TO_REMOVE_TEMP_FILE]

SEVERITY: WARNING

DESCRIPTION: DSS The Expression Manager was unable to remove a temporary file used during source code generation of expression with id %s. Removal of the temporary file %s failed due to IO Error: %s.

CAUSE: The Expression Manager was not able to remove a temporary file created during expression generation.

ACTION: Manually delete the specified temporary file.

PARAMS: The first parameter is the object id of the expression object that was being compiled. The second parameter is the name of the temporary file which could not be removed. The third parameter is the IO error reported by the operating system.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: