7.0-dm_api

DM_API


ERROR: [DM_API_F_CACHE_UNREADABLE]

SEVERITY: FATAL
DESCRIPTION: An unexpected internal error has occurred while reading query results from the query cache for your query.
CAUSE: The disk file containing your query results cache is unreadable.
ACTION: Report this problem to your Documentum System Administrator. You should also flush the query cache.
PARAMS:

ERROR: [DM_API_F_CACHE_CLOSE]

SEVERITY: FATAL
DESCRIPTION: An unexpected error has occurred while closing the query cache for your query.
CAUSE: This disk file containing your query results cache could not be closed for some reason.
ACTION: Report this problem to your Documentum System Administrator. You should also flush the query cache. The results displayed by your query will be complete unless other error messages have occurred.
PARAMS:

ERROR: [DM_API_F_BADRPCDLL]

SEVERITY: FATAL
DESCRIPTION: IIII You have a mismatched rpcdll.dll and dmcl.dll. rpc version: %d, rpc release: %d. Expected version: %d, expected release: %d
CAUSE: The rpcdll.dll and dmcl.dll libraries are incompatible and are different versions of the product.
ACTION: Verify the installation of rpcdll.dll and dmcl.dll and check your path for other possible dlls
PARAMS:

ERROR: [DM_API_F_CACHE_OBJECT]

SEVERITY: FATAL
DESCRIPTION: An unexpected error has occurred while loading an object from the query cache for your query.
CAUSE: An object in your query cache is not a valid object.
ACTION: Report this problem to your Documentum System Administrator. You should also flush the query cache. The results returned so far by your query may not be complete.
PARAMS:

ERROR: [DM_API_F_CACHE_MAP]

SEVERITY: FATAL
DESCRIPTION: An unexpected internal error has occurred while processing a cached query.
CAUSE: This is an internal inconsistency.
ACTION: Contact your site Documentum System Administrator. To get past this problem, try flushing the query cache and restarting your session. If that doesnt work, turn off query caching in your dmcl.ini file. $Id: dmassmbl.e,v 5.2 2003/05/12 16:34:04 nagboat Exp $ dmAssembly class errors
PARAMS:

ERROR: [DM_API_F_CACHE_READ]

SEVERITY: FATAL
DESCRIPTION: An unexpected internal error has occurred while reading query results from the query cache for your query.
CAUSE: The disk file containing your query results cache was unreadable for some reason.
ACTION: Report this problem to your Documentum System Administrator. You should also flush the query cache. The results returned so far by your query may not be complete.
PARAMS:

ERROR: [DM_API_F_INTERNAL]

SEVERITY: FATAL
DESCRIPTION: S An unexpected internal inconsistency has caused your operation to fail (%s).
CAUSE: Unknown.
ACTION: Provide this message, and its parameter, and any other recent messages from your session, and contact your Documentum site representative.
PARAMS: The parameter is an indication of where the error occurred.

ERROR: [DM_API_E_INVALID_TOKEN_SCOPE]

SEVERITY: ERROR
DESCRIPTION: S Invalid token scope (%s). It must be global or docbase.
CAUSE: wrong application token scope value is specified for gettoken.
ACTION: specify a correct application token scope value
PARAMS: S – The specified application token scope

ERROR: [DM_API_E_ISCACHED_NO_CACHE_NAME]

SEVERITY: ERROR
DESCRIPTION: A cache name must be supplied to the iscached API call.
CAUSE: You have specified a call to the iscached API call with no cache name.
ACTION: Supply a valid cache name, for example typecache.
PARAMS: None.

ERROR: [DM_API_E_MISSING_PASSWORD]

SEVERITY: ERROR
DESCRIPTION: A password must be provided.
CAUSE: A password was not provided for the API method resetpassword.
ACTION: specify a valid password
PARAMS: None

ERROR: [DM_API_E_NOT_IN_CACHE]

SEVERITY: ERROR
DESCRIPTION: S Document/object specified by %s does not exist in the cache.
CAUSE: You have specified an object id for an object which does not exist in the cache. Some API like lock requires the object to reside in cache before applying the operation.
ACTION: Fetch the object and re-try the same operation.
PARAMS: The object id.

ERROR: [DM_API_E_API_SHUTDOWN]

SEVERITY: ERROR
DESCRIPTION: S The DMCL has been disabled due to an internal error, command %s was not run. The process needs to be restarted.
CAUSE: Earlier errors of type DM_API_E_EXCEPTION or DM_API_E_EXCEPTION_ON_SESSION have occcurred.
ACTION: In its current state, the DMCL is no longer usable. The process will have to be restarted.
PARAMS: S – api command

ERROR: [DM_API_E_NO_MATCH]

SEVERITY: ERROR
DESCRIPTION: S There was no match in the docbase for the qualification: %s
CAUSE: The qualification you provided did not match any object.
ACTION: None required. If you think there really should have been a match reexamine your qualification, correct it, and resubmit it.
PARAMS: The qualification.

ERROR: [DM_API_E_ONELISTMSG]

SEVERITY: ERROR
DESCRIPTION: Cannot have multiple listmessage collections open simultaneously.
CAUSE: User tried to have more than one listmessage collection opened.
ACTION: Close the previous listmessage collection, before opening the next one.
PARAMS:

ERROR: [DM_API_E_BADSESS]

SEVERITY: ERROR
DESCRIPTION: S Bad session specifier %s, try using current.
CAUSE: You have incorrectly specified the session in your command line.
ACTION: Correct the session specification and retry the command. If you do not know what the correct session specification is, you could use current.
PARAMS: The incorrect session as specified in your command.

ERROR: [DM_API_E_NOT_SELECT]

SEVERITY: ERROR
DESCRIPTION: You have specified an unsupported statement type in a cachequery.
CAUSE: Only SELECT statements may be specified using cachequery.
ACTION: Resubmit the DQL statement using the readquery, query, or execquery method. If the statement is being run by an application, contact your Documentum System Administrator about having the application corrected.
PARAMS:

ERROR: [DM_API_E_NOLAST]

SEVERITY: ERROR
DESCRIPTION: Cannot use last for document/object id. Must fetch or create document/object first.
CAUSE: You have specified last in place of a document or object id, but no object is active.
ACTION: Specify the object id explicitly in your command and retry.
PARAMS: None.

ERROR: [DM_API_E_CANNOT_FETCH_POLICY]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch a business policy with object id %s.
CAUSE: A business policy object with the supplied id could not be found.
ACTION: Specify a valid business policy object id.
PARAMS: The parameter is the business policy object id that was supplied.

ERROR: [DM_API_E_NOPASSWORD]

SEVERITY: ERROR
DESCRIPTION: There is no password argument specified.
CAUSE: You have not specified the password which is required to electronically sign off an object.
ACTION: Please specify the valid password of the user who is signing off the object.
PARAMS:

ERROR: [DM_API_E_BADSTAMP]

SEVERITY: ERROR
DESCRIPTION: S Bad queue stamp specifier for queue %s.
CAUSE: Your command did not specify a stamp.
ACTION: The stamp is the unique identifier for the object you wish to dequeue. It must be specified on this command.
PARAMS: The name of the queue.

ERROR: [DM_API_E_MUSTBE_NEXT]

SEVERITY: ERROR
DESCRIPTION: You must specify next as the state name to promote to.
CAUSE: This is to reserve a field for Promote API to easily expand into state network model. Currently, next is only aceptable state, which simply means the next state of the current state.:wq
ACTION:
PARAMS:

ERROR: [DM_API_E_DOCBASE_SCOPE_ID]

SEVERITY: ERROR
DESCRIPTION: L Could not connect to docbase. Docbase id %d could not be found.
CAUSE: The request failed due to an unknown docbase name in the scope setting. Unless the requested command has a scope argument the scope is derived from the sessionconfigs docbase_scope attribute.
ACTION: Check the request to see if the scope argument is valid. If it is, verify that the requested docbase is available. Check that the application is using a docbroker that the requested server projects to. Try connecting to the docbase directly through the connect api or login.
PARAMS: %1s – the docbase id being searched for

ERROR: [DM_API_E_UNKNOWN_SECURE_FLAG]

SEVERITY: ERROR
DESCRIPTION: S Unknown secure connect flag %s is specified.
CAUSE: Unknown secure connect flag specified. Valid secure connect flags are secure, native, try_secure_first and try_native_first.
ACTION: specify a valid secure connect flag.
PARAMS: Secure connect flag specified.

ERROR: [DM_API_E_INVALID_TYPE_FOR_METHOD]

SEVERITY: ERROR
DESCRIPTION: SSS Cannot perform %s method on supplied object of id (%s) since it is not of type (%s).
CAUSE: The specified operation not supported on this type of sysobject.
ACTION: None.
PARAMS:

ERROR: [DM_API_E_NOCACHE]

SEVERITY: ERROR
DESCRIPTION: Internal error, cache is missing.
CAUSE: This is a very unlikely event. Your internal object cache has been destroyed.
ACTION: This is not recoverable. You must restart your session.
PARAMS: None.

ERROR: [DM_API_E_QUERY_FAIL]

SEVERITY: ERROR
DESCRIPTION: S Query failed: %s
CAUSE: Your query failed. Either you specified the query incorrectly on the command line, or the query executed, but failed to return a query results collection. This may be a query that was run on behalf of a non-query method that you have invoked. It may be that a qualification that you have provided (for the ID or RETRIEVE methods, for example) was in error.
ACTION: Examine the rest of the error messages on your sessions message queue. If there are no other messages, then the query was incorrectly specified on the command line. Examine your command line and make the necessary corrections. If there are additional messages, they will explain what the cause of the failure was, and what to do about it.
PARAMS: The query.

ERROR: [DM_API_E_FLUSH_DD_CACHE_NO_KEY]

SEVERITY: ERROR
DESCRIPTION: A cache key must be supplied to the flush API call when ddcache is specified.
CAUSE: You have specified a call to the flush API for the ddcache without specifying a cache key. The cache key indicates for which type the Data Dictionary information should be flushed.
ACTION: Supply a key that is the name of an object type.
PARAMS: None.

ERROR: [DM_API_E_SCHD_POLICY_NO_STATE]

SEVERITY: ERROR
DESCRIPTION: A scheduled policy event requires a state name specified.
CAUSE: User tries to schedule a policy event (promote, demote, suspend, resume) without providing a source (or target) state name/position.
ACTION: Supply a source or target state name/position.
PARAMS:

ERROR: [DM_API_E_NO_COLLECTION]

SEVERITY: ERROR
DESCRIPTION: There are no more available collection object for the current session.
CAUSE: User has used all available collection. Current limit is 10 per session.
ACTION: Close some unused collections.
PARAMS:

ERROR: [DM_API_E_NOTASKNUM]

SEVERITY: ERROR
DESCRIPTION: No task number specified during router operations.
CAUSE: You have not specified a task number during a router operation. (i.e. forward, reverse, …)
ACTION: Specify the task number during this router operation.
PARAMS:

ERROR: [DM_API_E_BAD_POSITION]

SEVERITY: ERROR
DESCRIPTION: S Invalid position argument (%s) to seek method
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_NODEVNAME]

SEVERITY: ERROR
DESCRIPTION: S No device name was given for command %s.
CAUSE: The device name is required for this command.
ACTION: Correct the command to specify the device name.
PARAMS: The command as specified.

ERROR: [DM_API_E_NOTYPE]

SEVERITY: ERROR
DESCRIPTION: S Type name %s is not a valid type.
CAUSE: The specified typename is not valid.
ACTION: If this is a typename that you have specified explicitly on a command line, ensure that the type exists, correct the command and retry. Otherwise, this is a type that a command requires internally, and it does not exist. This may be an internal problem. Report this error to your Documentum site representative.
PARAMS: The name of the type as passed to the API.

ERROR: [DM_API_E_CANT_WITH_OPEN_TRAN]

SEVERITY: ERROR
DESCRIPTION: SD You cannot perform %s operation since there is an open transaction in this session %s.
CAUSE: Since attach,promote,demote,suspend,continue all inlvolve some form of procedure execution in which the sysobject changes are committed. This is to prevent hanging/save failure from happening.
ACTION:
PARAMS:

ERROR: [DM_API_E_NOFOLDID]

SEVERITY: ERROR
DESCRIPTION: No folder id given for a link/unlink command.
CAUSE: The folder id is required for link and unlink.
ACTION: Correct the command to specify a folder id.
PARAMS: None.

ERROR: [DM_API_E_NOSESS]

SEVERITY: ERROR
DESCRIPTION: No session is currently active.
CAUSE: You are not connected with a session.
ACTION: Your session may have been dropped due to inactivity. You must start up another session.
PARAMS: None.

ERROR: [DM_API_E_ERROR]

SEVERITY: ERROR
DESCRIPTION: General internal error: API has failed.
CAUSE: Unknown internal problem.
ACTION: This error is unrecoverable. Report this error message, and any other recent error messages from your session, to your Documentum site representative.
PARAMS: None.

ERROR: [DM_API_E_BAD_EXTENSION_FOR_BATCH]

SEVERITY: ERROR
DESCRIPTION: SS The extension of the input file, %s, is not allowed for %s in batch mode.
CAUSE: We currently only support tar format file with extension tar in batch addrendition.
ACTION: We only support tar format file in batch addrendition. You have to specify a tarred file with extension tar.
PARAMS: file name and name of the API.

ERROR: [DM_API_E_BAD_DIRECTION]

SEVERITY: ERROR
DESCRIPTION: S An improper direction (%s) was specified in a seek.
CAUSE: Direction specification in a seek must be one of C, B, E
ACTION: Use a valid direction specification
PARAMS: The direction specification that was supplied.

ERROR: [DM_API_E_COMMAND_OBSOLETE]

SEVERITY: ERROR
DESCRIPTION: S The API command %s is no longer supported.
CAUSE: An obsolete API command has requested.
ACTION: The application should be modified to no longer depend on the obsolete command.
PARAMS: The command requested.

ERROR: [DM_API_E_NO_REMOTE_POLICY]

SEVERITY: ERROR
DESCRIPTION: L You cannot attach to a non-local business policy object from docase id %d.
CAUSE: The policy object id is either a bogus one or is foreign.
ACTION:
PARAMS:

ERROR: [DM_API_E_MISS_PACKAGE_TYPE]

SEVERITY: ERROR
DESCRIPTION: Parameter, package type, is missing.
CAUSE: Parameter, package type, was not specified.
ACTION: Specify package type.
PARAMS:

ERROR: [DM_API_E_NOPRIORITY]

SEVERITY: ERROR
DESCRIPTION: S No priority specified for routing.
CAUSE:
ACTION:
PARAMS: None.

ERROR: [DM_API_E_BADID]

SEVERITY: ERROR
DESCRIPTION: S Bad ID given: %s
CAUSE: You have specified an invalid id.
ACTION: Retry with a valid id definition.
PARAMS:

ERROR: [DM_API_E_MISSING_CONTAINMENT_TYPE]

SEVERITY: ERROR
DESCRIPTION: S A containment desc of %s was supplied but its corresponding containment type is missing.
CAUSE: The containment type must be supplied if the containment description is supplied.
ACTION: Supply the corresponding containment type.
PARAMS:

ERROR: [DM_API_E_NO_USER]

SEVERITY: ERROR
DESCRIPTION: Need to specifiy an user.
CAUSE: Need to specifiy a user as the performer.
ACTION: Specify an user name.
PARAMS:

ERROR: [DM_API_E_BADCMD]

SEVERITY: ERROR
DESCRIPTION: S Bad API command %s
CAUSE: An API command has been incorrectly formed.
ACTION: If the parameter is , make sure that no spaces precede your specified command in the command line. Otherwise, check to be sure that the command you have specified is a valid API command. Reformulate and retry your command.
PARAMS: The command as specified, or .

ERROR: [DM_API_E_DOCBASE_SCOPE]

SEVERITY: ERROR
DESCRIPTION: S Could not connect to docbase. Docbase %s could not be found.
CAUSE: The request failed due to an unknown docbase name in the scope setting. Unless the requested command has a scope argument the scope is derived from the sessionconfigs docbase_scope attribute.
ACTION: Verify that the requested docbase is available. Check that the application is using a docbroker that the requested server projects to. Try connecting to the docbase directly through the connect api or login.
PARAMS: %1s – the user-specified docbase name

ERROR: [DM_API_E_NOSCOPE]

SEVERITY: ERROR
DESCRIPTION: The required scope argument is missing.
CAUSE: The request failed due to an invalid docbase scope argument.
ACTION: Modify request to include scope value.
PARAMS: None

ERROR: [DM_API_E_NO_FILE]

SEVERITY: ERROR
DESCRIPTION: S No file name given for command %s.
CAUSE: A file name is required for this command.
ACTION: Correct the command to specify a file name.
PARAMS: The command as specified

ERROR: [DM_API_E_NODBPASSWD]

SEVERITY: ERROR
DESCRIPTION: No database password provided for a connection.
CAUSE: The fourth argument has not been provided for a connect statement.
ACTION: Provide a complete connect statement.
PARAMS:

ERROR: [DM_API_E_INVALID_ARG_APPLY]

SEVERITY: ERROR
DESCRIPTION: SSS Invalid value (%s) for the %s argument of %s apply method.
CAUSE: Invalid value for an argument of an apply method.
ACTION: Specify a valid value for the argument.
PARAMS:

ERROR: [DM_API_E_NO_ACL_SOURCE]

SEVERITY: ERROR
DESCRIPTION: The ACL inheritance source is missing.
CAUSE: The inheritance source of useacl cmd is missing.
ACTION:
PARAMS:

ERROR: [DM_API_E_NO_CACHE_NAME]

SEVERITY: ERROR
DESCRIPTION: The name of the global cache to be flushed is missing.
CAUSE: The name of the global cache to be flushed is missing from the flushglobalcache method.
ACTION: Provide the cache name in the flushglobalcache method. Currently, only user cache is allowed.
PARAMS:

ERROR: [DM_API_E_EXIST]

SEVERITY: ERROR
DESCRIPTION: S Document/object specified by %s does not exist.
CAUSE: You have specified an object id for an object which does not exist.
ACTION: Ensure that you are specifying the correct object id. Remember that you save a new object, it gets a new id. If there are additional error messages on your session, they may contain information which is helpful as well.
PARAMS: The object id.

ERROR: [DM_API_E_MISS_PACKAGE_NAME]

SEVERITY: ERROR
DESCRIPTION: Parameter, package name, is missing.
CAUSE: Parameter, package name, was not specified.
ACTION: Specify package name.
PARAMS:

ERROR: [DM_API_E_INVALID_TICKET_SCOPE]

SEVERITY: ERROR
DESCRIPTION: S Invalid login ticket scope (%s). It must be global, docbase, or server.
CAUSE: wrong login ticket scope value is specified for getlogin.
ACTION: specify a correct login ticket scope value
PARAMS: S – The specified login ticket scope

ERROR: [DM_API_E_MISS_LINK_NAME]

SEVERITY: ERROR
DESCRIPTION: Missing parameter link name.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_FLUSH_DD_CACHE_BAD_KEY]

SEVERITY: ERROR
DESCRIPTION: S A cache key (%s) was supplied to the flush ddcache API call that is not the name of a type.
CAUSE: The cache key you specified is not the name of a type.
ACTION: Supply a key that is the name of an object type.
PARAMS: None.

ERROR: [DM_API_E_NOPERMIT]

SEVERITY: ERROR
DESCRIPTION: The accessor permit is missing.
CAUSE: Accessor permit is missing from the cmd line.
ACTION: Provide the accessor permit.
PARAMS:

ERROR: [DM_API_E_EXPECT_BOOL]

SEVERITY: ERROR
DESCRIPTION: ISS A null or boolean value was expected for positional parameter %d. Bad value: %s. This parameter specifies %s.
CAUSE: The command expected to parse a boolean or no value at all. Boolean arguments can take the form: t, T, f, F, true, false, TRUE, FALSE
ACTION:
PARAMS:

ERROR: [DM_API_E_NULL_TICKET]

SEVERITY: ERROR
DESCRIPTION: A login ticket must be provided.
CAUSE: Missing login ticket argument for the API method dumploginticket
ACTION: Specify a login ticket
PARAMS: None

ERROR: [DM_API_E_POLICY_STATE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: DS The business policy with object id %s does not have a state named %s.
CAUSE: The supplied state name could not be found in the given business policy.
ACTION: Specify a valid state name for the business policy.
PARAMS: The first parameter is the business policy object id that was supplied. The second parameter is the state name supplied.

ERROR: [DM_API_E_FACILITY_UNKNOWN]

SEVERITY: ERROR
DESCRIPTION: S The specified facility (%s) is not a valid trace facility.
CAUSE: The command specified an invalid facility name.
ACTION: Check command syntax – check that facility name is upper case.
PARAMS: %1s – the user-specified facility name

ERROR: [DM_API_E_NO_PERMIT_TYPE]

SEVERITY: ERROR
DESCRIPTION: No value for permit_type was specified.
CAUSE: No permit_type value was specified in the API
ACTION: Check the API syntax and ensure that a permit_type value is specified
PARAMS:

ERROR: [DM_API_E_BAD_ARGS]

SEVERITY: ERROR
DESCRIPTION: SS Invalid or insufficient arguments for %s for %s API
CAUSE: User did not specify valid values for required argument while executing the specified API.
ACTION: Specify value for required arguments and retry.
PARAMS: S – argument name(s) S – API Name.

ERROR: [DM_API_E_INVALID_MACHINE_ONLY]

SEVERITY: ERROR
DESCRIPTION: S Invalid machine_only parameter value (%s). It must be T or t.
CAUSE: Wrong machine_only parameter value is specified for gettokn.
ACTION: Specify a correct value for machine_only.
PARAMS: S – The specified value for machine_only parameter

ERROR: [DM_API_E_NOTYPE2]

SEVERITY: ERROR
DESCRIPTION: No type was specified.
CAUSE: You have specified a command for which the type must be specified.
ACTION: Add the type to your command, and retry.
PARAMS: None.

ERROR: [DM_API_E_NOOSPASSWD]

SEVERITY: ERROR
DESCRIPTION: No operating system password has been provided for a connection.
CAUSE: The third argument has not been provided for a connect statement.
ACTION: Provide a complete connect statement.
PARAMS:

ERROR: [DM_API_E_MISS_INPUT_PORT_NAME]

SEVERITY: ERROR
DESCRIPTION: The parameter, input port name, is missing.
CAUSE: Parameter, input port name, is required for the command.
ACTION: Specify the input port name in the command.
PARAMS:

ERROR: [DM_API_E_MISS_ACTIVITY_DEF_ID]

SEVERITY: ERROR
DESCRIPTION: Missing parameter activity definition id.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_NOEVENTNAME]

SEVERITY: ERROR
DESCRIPTION: No event name specified during register/unregister operations.
CAUSE: You have not specified an event name during event register/unregister operation.
ACTION: Specify the event name.
PARAMS:

ERROR: [DM_API_E_DEQUEUE_FAIL]

SEVERITY: ERROR
DESCRIPTION: S Dequeue operation on queue item %s failed
CAUSE: The requested dequeue failed during server execution.
ACTION: There will be additional error messages queued on your session. Those error messages will contain information on why this operation failed. Follow the suggested actions in those error messages to correct this problem.
PARAMS: The name of the queue.

ERROR: [DM_API_E_FLUSH_BAD_ARG]

SEVERITY: ERROR
DESCRIPTION: S The flush method had an unsupported cache name argument: %s.
CAUSE: A flush method was invoked with a cachename argument that is not supported. Currently only querycache is supported.
ACTION: Change the cachename argument to a supported cachename and retry.
PARAMS:

ERROR: [DM_API_E_DESCRIBE_TABOWNER]

SEVERITY: ERROR
DESCRIPTION: To execute this describe table operation against the current server you must supply the table owner name in the command (ie. describe table owner_name.table_name).
CAUSE: The server to which the application is connected does not support the describe table command on system tables (beginning with dm). The application is likely connected to an older server which cannot process the requested action.
ACTION: If possible upgrade the server to resolve the problem. Otherwise issue the owner name along with the table name in the describe command.
PARAMS: None

ERROR: [DM_API_E_DOCBASE_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: S You cannot specify a docbase name (%s) if you use a session in authenticate API.
CAUSE: If a session is specified in the authenticate API, no docbase name should be used.
ACTION: Verify your argument of authenticate API to meet this requirement.
PARAMS: S – Docbase name.

ERROR: [DM_API_E_BADATTRSTATE]

SEVERITY: ERROR
DESCRIPTION: SS Attribute name %s for policy has incorrect value %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_FLUSH_REGISTRY_CACHE_NO_KEY]

SEVERITY: ERROR
DESCRIPTION: A cache key must be supplied to the flush API call when registrycache is specified.
CAUSE: You have specified a call to the flush API for the registrycache without specifying a cache key. The cache key indicates for which type the in memory registry information should be flushed.
ACTION: Supply a key that is the name of an object type.
PARAMS: None.

ERROR: [DM_API_E_BADSCOPE]

SEVERITY: ERROR
DESCRIPTION: S Docbase scope identifier (%s) is not valid.
CAUSE: The request failed due to an invalid docbase scope argument. The scope value is specified directly on some commands (eg getconnection takes a scope argument) – and is otherwise picked up from the sessionconfigs docbase_scope attribute.
ACTION: Change the scope value – either on the command line or in the sessionconfig docbase_scope field – to be a legal scope value.
PARAMS: %1s – the user-specified scope value

ERROR: [DM_API_E_MISS_ACT_NAME]

SEVERITY: ERROR
DESCRIPTION: The parameter, activity name, is missing.
CAUSE: Parameter, activity name, is required for the command.
ACTION: Specify the activity name in the command.
PARAMS:

ERROR: [DM_API_E_BADDATE]

SEVERITY: ERROR
DESCRIPTION: SS You have specified an unrecognized date representation %s based on format %s
CAUSE: The date representation shown does not conform to the date formats that Documentum recognizes, or the date is not in the valid date range. Dates prior to the year 1970 may not be specified.
ACTION: Correct the date.
PARAMS: The incorrectly specified date.

ERROR: [DM_API_E_ACCESS]

SEVERITY: ERROR
DESCRIPTION: S Document/object specified by %s cannot be accessed.
CAUSE: You have specified an object id for an object which cannot be accessed.
ACTION: Ensure that you are specifying the correct object id. Remember that you save a new object, it gets a new id. If there are additional error messages on your session, they may contain information which is helpful as well.
PARAMS: The object id.

ERROR: [DM_API_E_MISS_DEST_PORT]

SEVERITY: ERROR
DESCRIPTION: Missing parameter destination port.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_EXCEPTION]

SEVERITY: ERROR
DESCRIPTION: S An unexpected error has caused the current command to be aborted. A detailed description of the error can be found in %s.
CAUSE: An unknown error has caused a memory access violation.
ACTION: Provide this message, and the contents of the error report file, and contact your Documentum site representative.
PARAMS: S – pathname to error file dmcl_err_pid__.txt

ERROR: [DM_API_E_NOUSERNAME]

SEVERITY: ERROR
DESCRIPTION: No user name have been provided for a connection.
CAUSE: The second argument has not been provided for a connect statement.
ACTION: Provide a complete connect statement.
PARAMS:

ERROR: [DM_API_E_BAD_PAGE_MODIFIER]

SEVERITY: ERROR
DESCRIPTION: S The page_modifier, %s, is reserved for internal use.
CAUSE: The page_modifier specified by user is reserved for internal use.
ACTION: We have reserved dm_batch in page_modifier in order to process addrendition in batch mode. You have to specify a different value for the page_modifier
PARAMS: The page_modifier.

ERROR: [DM_API_E_OUT_OF_MEMORY]

SEVERITY: ERROR
DESCRIPTION: There is not enough memory for creating the object.
CAUSE: System needs more memory
ACTION: Add more memory or reduce the system workload
PARAMS: None

ERROR: [DM_API_E_CANNOT_FETCH_REMOTE_POLICY]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch a remote business policy with object id %s.
CAUSE: A business policy object with the supplied id could not be found.
ACTION: Verify your access to the remote docbase. Specify a valid business policy object id.
PARAMS: The parameter is the business policy object id that was supplied.

ERROR: [DM_API_E_NOQUERY]

SEVERITY: ERROR
DESCRIPTION: No query has been run. Cannot use a query collection id.
CAUSE: You are attempting to look up an object and its typed based on a query collection which has not had a query run yet.
ACTION: Run a query first.
PARAMS: None.

ERROR: [DM_API_E_CONFIGURATION]

SEVERITY: ERROR
DESCRIPTION: SS The value %s is not a valid setting for %s in the dmcl.ini initialization file.
CAUSE: An invalid parameter value was specified in the dmcl.ini API initialization file.
ACTION: Read the description of the parameter in the dmclfull.ini file.
PARAMS: The parameter value and the parameter name from the dmcl.ini.

ERROR: [DM_API_E_BOOLEAN_FLAG]

SEVERITY: ERROR
DESCRIPTION: S The value %s is not valid. The boolean flag is either T or F.
CAUSE: The value of the boolean flag in the command needs to be either T or F.
ACTION: Change the value of the boolean flag and try again.
PARAMS:

ERROR: [DM_API_E_COMMAND_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: SS Server version (%s) does not support the method (%s).
CAUSE: Pre-5.3 Content Server does not support the API the method.
ACTION: Do not use the method with pre-53 Content Server.
PARAMS: S – target server version string S – command name

ERROR: [DM_API_E_ISCACHED_NO_CACHE_KEY]

SEVERITY: ERROR
DESCRIPTION: A cache key must be supplied to the iscached API call.
CAUSE: You have specified a call to the iscached API call with no cache key. The cache key indicates what to look for in the named cache.
ACTION: Supply a key that is appropriate for the named cache.
PARAMS: The parameter is the name of the cache.

ERROR: [DM_API_E_PUBLISH_DD_MISSING_PARAMETER]

SEVERITY: ERROR
DESCRIPTION: When calling the publish_dd api, the 1st parameter (locale) is optional. The 2nd parameter (type_name) is optional, but must be present if the 3rd parameter (attribute) is specified.
CAUSE: The syntax was incorrect on the publish_dd api call.
ACTION: The api call takes 3 parameters, locale name, type name, and attribute name. All 3 are optional, but if the attribute name is present, the type name must also be present.
PARAMS:

ERROR: [DM_API_E_NO_APPLICATION_PERMIT]

SEVERITY: ERROR
DESCRIPTION: The application_permit value was not specified.
CAUSE: The application_permit value is missing.
ACTION: Specify the application_permit value
PARAMS:

ERROR: [DM_API_E_BADDATATYPE]

SEVERITY: ERROR
DESCRIPTION: S Bad datatype or value conversion for attribute %s.
CAUSE: You have specified an attribute, along with a datatype or a value. The datatype was not a valid docuserver datatype, or the value was incompatible with the datatype of the specified attribute.
ACTION: Correct the command as appropriate and retry.
PARAMS: The name of the attribute.

ERROR: [DM_API_E_BADATTRINDX]

SEVERITY: ERROR
DESCRIPTION: SI Attribute name %s for document/object has incorrect index %d
CAUSE: Attribute name was supplied with an incorrect index.
ACTION: Check to make sure that the index is within bounds of the current number of attributes.
PARAMS: None.

ERROR: [DM_API_E_GETHOSTBYNAME_FAILED]

SEVERITY: ERROR
DESCRIPTION: OS Error has occurred in gethostbyname() or gethostbname_r(). Retry could resolve the issue.
CAUSE: Due to some threading issues in Unix gethostbyname() or gethostbyname_r() may return NULL
ACTION: Abort DMCL client creation. Client Application (DFC/WDK) can retry.
PARAMS:

ERROR: [DM_API_E_NO_EVENT_NAME]

SEVERITY: ERROR
DESCRIPTION: S No event name given for command %s.
CAUSE: An event name is required for this command.
ACTION: Correct the command to specify an event name.
PARAMS: The command as specified.

ERROR: [DM_API_E_BADSEVERITY]

SEVERITY: ERROR
DESCRIPTION: S Bad severity level given: %s
CAUSE: You have specified an invalid severity level.
ACTION: Retry with a valid severity level (0 ~ 4).
PARAMS:

ERROR: [DM_API_E_MUSTBE_BASE_PREV]

SEVERITY: ERROR
DESCRIPTION: You must specify base or previous as the state name to demote to.
CAUSE: This is to reserver a field for Demote API to easily expand into state network model. Currently, base means demoting to base base state previous means demoting to the original state.
ACTION:
PARAMS:

ERROR: [DM_API_E_INVALID_PERMIT]

SEVERITY: ERROR
DESCRIPTION: I An invalid accessor_permit value of %d was specified.
CAUSE: An invalid accessor_permit value was specified.
ACTION: Specify a valid accessor_permit value
PARAMS:

ERROR: [DM_API_E_CANT_UPDATE]

SEVERITY: ERROR
DESCRIPTION: S Cannot Save/Check-in object because the object is marked invalid. This is most likely due to an error from a prior operation performed on the object.
CAUSE: One or more operations has failed during this update. Consult the following error message(s) for more help.
ACTION: Try again after fixing previous problems.
PARAMS:

ERROR: [DM_API_E_NODOCBASE]

SEVERITY: ERROR
DESCRIPTION: No document base has been provided for a connection.
CAUSE: The first argument has not been provided for a connect statement.
ACTION: Provide a complete connect statement.
PARAMS:

ERROR: [DM_API_E_NO_UL_SUPPORT]

SEVERITY: ERROR
DESCRIPTION: The server does not support NT Unified Logon.
CAUSE: The server is not running under NT or the old docbroker is running
ACTION: Make sure the server and the docbroker support NT Unified Logon
PARAMS:

ERROR: [DM_API_E_INVALID_INPUT]

SEVERITY: ERROR
DESCRIPTION: S Input string (%s) must have prefix DM_TICKET= or DM_TOKEN.
CAUSE: The input string is neither a login ticket nor an application access control token.
ACTION: Specifiy a valid login ticket or application access control token.
PARAMS: the input string.

ERROR: [DM_API_E_MISS_SRC_PORT]

SEVERITY: ERROR
DESCRIPTION: Missing parameter source port.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_INVALID_FORCE_AUTH]

SEVERITY: ERROR
DESCRIPTION: S Invalid value (%s) for connect argument force_authenticate. It must be T, t, F, or f.
CAUSE: Invalid value for connect argument force_authenticate
ACTION: Specify a valid value for connect argument force_authenticate
PARAMS:

ERROR: [DM_API_E_NOPOLIID]

SEVERITY: ERROR
DESCRIPTION: you need to specify a valid policy object while doing an Attach.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_STATE_WITH_NO_POLICY]

SEVERITY: ERROR
DESCRIPTION: S The state name parameter (%s) to the type api cannot be supplied without a business policy object id.
CAUSE: The business policy id was omitted or NULL.
ACTION: Specify a valid business policy id if a state name is used.
PARAMS: The parameter is the state name that was supplied.

ERROR: [DM_API_E_INVALID_TIMEOUT]

SEVERITY: ERROR
DESCRIPTION: S Invalid timeout parameter value (%s). It must be a valid integer.
CAUSE: Wrong timeout parameter value is specified for getlogin/gettoken.
ACTION: Specify a correct value for timeout
PARAMS: S – The specified value for timeout parameter

ERROR: [DM_API_E_NO_XPERMIT]

SEVERITY: ERROR
DESCRIPTION: The accessor_xpermit value was not specified.
CAUSE: The accessor_xpermit value is missing.
ACTION: Specify the accessor_xpermit value
PARAMS:

ERROR: [DM_API_E_CANT_WITHOUT_OPEN_TRAN]

SEVERITY: ERROR
DESCRIPTION: S You cannot perform %s operation without an open transaction in this session.
CAUSE: The specified operation needs to be run under an open transaction.
ACTION: Issue a begintran before running the specified operation.
PARAMS:

ERROR: [DM_API_E_MISS_ROUTE_ID]

SEVERITY: ERROR
DESCRIPTION: The parameter route case identifier is missing.
CAUSE: The route case identifier parameter is missing.
ACTION: Specify a route case identifier.
PARAMS:

ERROR: [DM_API_E_MISS_DEST_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: Missing parameter destination activity.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_METHOD_NOT_APPLICABLE]

SEVERITY: ERROR
DESCRIPTION: SS The method %s is not applicable to type %s.
CAUSE: The attempted operation is not supported by the type.
ACTION: Use the method supported by the type instead.
PARAMS: S – method name S – type name

ERROR: [DM_API_E_NO_PAGE_MODIFIER_FOR_BATCH]

SEVERITY: ERROR
DESCRIPTION: SS The page_modifier, %s, is not allowed for %s in batch mode.
CAUSE: The page_modifier isnt allowed when processing the operation in batch mode.
ACTION: Either set the batch_flag to false or remove the page_modifier in the operation.
PARAMS: The page_modifier and API name of the operation.

ERROR: [DM_API_E_MISS_ROUTE_COND]

SEVERITY: ERROR
DESCRIPTION: The parameter route condition is missing.
CAUSE: The route condition parameter is missing.
ACTION: Specify a route condition.
PARAMS:

ERROR: [DM_API_E_BADQUERY]

SEVERITY: ERROR
DESCRIPTION: S No query has been run for command %s.
CAUSE: You have specified next or close on a null query result collection.
ACTION: You probably ran a query that failed and returned a null collection. Check the error messages for your session they should provide an explanation as to why your query failed. Correct your query and run it again. Check to be sure you get a collection back before issuing a next or close command.
PARAMS: The command specified.

ERROR: [DM_API_E_NONAME]

SEVERITY: ERROR
DESCRIPTION: The accessor name is missing.
CAUSE: Accessor name is missing from the cmd line.
ACTION: Provide the accessor name.
PARAMS:

ERROR: [DM_API_E_DISTTRANS_UNSUPPORTED]

SEVERITY: ERROR
DESCRIPTION: It is disallowed to update through a reference or a replica while a user transaction is open.
CAUSE: The distributed transaction is disallowed in this release.
ACTION: Check if begintrans has been issued and only update through a reference or a replica outside of the transaction.
PARAMS:

ERROR: [DM_API_E_AUTH_CMD_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: S The target server of version (%s) does not support authenticate command.
CAUSE: Pre-5.2 server does not support API command authenticate.
ACTION: Use other command such as connect to authenticate user.
PARAMS: S – target server version string

ERROR: [DM_API_E_EXCEPTION_ON_SESSION]

SEVERITY: ERROR
DESCRIPTION: SS An unexpected error has caused the command %s to be aborted. The session and all associated subconnections have been disabled. A detailed description of the error can be found in %s.
CAUSE: An unknown error has caused a memory access violation.
ACTION: Provide this message, and the contents of the error report file, and contact your Documentum site representative.
PARAMS: S – api command S – pathname to error file dmcl_err_pid__.txt

ERROR: [DM_API_E_BAD_TYPE]

SEVERITY: ERROR
DESCRIPTION: DS The object, %s, is not type, %s.
CAUSE: The object and type specified do not agree.
ACTION: Check the existence of the objct or the type of the object.
PARAMS: D – object ID S – type

ERROR: [DM_API_E_MISS_ACTIVITY_NAME]

SEVERITY: ERROR
DESCRIPTION: Missing parameter activity name.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_DECODING_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS Decoding %s (%s) failed.
CAUSE: The given login ticket or applicatiob access control token is corrupted.
ACTION: Make sure the specified login ticket or token is valid.
PARAMS: the first parameter tells whether this is login ticket or token. The second parameter is the login ticket or token.

ERROR: [DM_API_E_NOID]

SEVERITY: ERROR
DESCRIPTION: S No id given for command %s.
CAUSE: An object id is required for this command.
ACTION: Correct the command to specify an object id.
PARAMS: The command as specified.

ERROR: [DM_API_E_ISCACHED_BAD_CACHE_NAME]

SEVERITY: ERROR
DESCRIPTION: S %s is not a valid cache name for the iscached API call.
CAUSE: You have specified a call to the iscached API call with an invalid cache name.
ACTION: Supply a valid cache name, for example typecache.
PARAMS: None.

ERROR: [DM_API_E_VDMPATH_SORTBY]

SEVERITY: ERROR
DESCRIPTION: S %s is not a valid attribute to sort by
CAUSE: The attribute specified in the sort by parameter is not allowed.
ACTION: Choose a different attribute by which to exclude multiple versions of components in the path.
PARAMS:

ERROR: [DM_API_E_UNRECOGNIZED_PARAMETER]

SEVERITY: ERROR
DESCRIPTION: S An unrecongized parameter with value %s was specified. Check the API syntax and the parameter and try again.
CAUSE: An unrecognized parameter was encountered in the API statement.
ACTION: Check the parameter and API syntax and try again.
PARAMS:

ERROR: [DM_API_E_CANT_SEEK]

SEVERITY: ERROR
DESCRIPTION: Cant perform a seek operation for this content
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_CHECK_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: Paramter check activity is invalid.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_FLUSH_NO_ARG]

SEVERITY: ERROR
DESCRIPTION: The flush method had a missing required cachename argument.
CAUSE: A flush method was invoked without the required cachename arguement.
ACTION: Add the cachename argument (currently only querycache is supported) and retry.
PARAMS:

ERROR: [DM_API_E_BADFILE_FORMAT]

SEVERITY: ERROR
DESCRIPTION: S File format for file %s is either incorrect or missing.
CAUSE: The file format for a method that adds a new file to a document is either missing or incorrect.
ACTION: Insure that the file format has been specified. Make sure that the file format matches those listed in dm_format objects.
PARAMS: The file that is being added.

ERROR: [DM_API_E_UPDATE_BAD_ATTR]

SEVERITY: ERROR
DESCRIPTION: S The attribute %s is not updateable.
CAUSE: The attribute you are attempting to set is not an updateable attribute.
ACTION: Internal and readonly attributes are not updateable. Remove the reference(s) to attribute(s) beginning with i_ or _r, from your update or create object statement.
PARAMS:

ERROR: [DM_API_E_ACTION]

SEVERITY: ERROR
DESCRIPTION: specify TRUE/FALSE or do not specify anything
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_NOFOLDER]

SEVERITY: ERROR
DESCRIPTION: S Folder with the path %s does not exist.
CAUSE: You have tried to fetch a folder that does not exist.
ACTION: Double check the path that you specified and ensure that it is correct. The folder may have been deleted. Also check any other error messages queued on your session to see if they also reference this folder.
PARAMS: The path name specified in the command.

ERROR: [DM_API_E_BADOBJ]

SEVERITY: ERROR
DESCRIPTION: S Command %s returned an invalid document/object id.
CAUSE: Your command has returned an invalid (null) object id.
ACTION: The command should have generated other error messages which will explain the cause for this failure. Check the rest of the message queue, and follow whatever actions are suggested in the other error messages.
PARAMS: The command, as specified.

ERROR: [DM_API_E_MISS_SRC_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: Missing parameter source activity.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_INVALID_SINGLE_USE]

SEVERITY: ERROR
DESCRIPTION: S Invalid single_use parameter value (%s). It must be T, t, F, or f.
CAUSE: Wrong single_use parameter value is specified for getlogin.
ACTION: Specify a correct value for single_use parameter.
PARAMS: S – The specified value for single_use parameter

ERROR: [DM_API_E_SAVE_TYPE]

SEVERITY: ERROR
DESCRIPTION: S The internal type, %s, can not be saved.
CAUSE: Internal types cant be saved.
ACTION: create and save a non-internal type.
PARAMS: S – type name

ERROR: [DM_API_E_NOLABEL]

SEVERITY: ERROR
DESCRIPTION: No version label specified during appendcomp/insertcomp operations.
CAUSE: You have not specified a version label during appendcomp or insertcomp operation.
ACTION: Specify the version label during the appendcomp or insertcomp operation.
PARAMS:

ERROR: [DM_API_E_CAUSE]

SEVERITY: ERROR
DESCRIPTION: an invalid value for check activity was specified or parameter check activity should not be specified.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_POLICY_WITH_NO_STATE]

SEVERITY: ERROR
DESCRIPTION: D If a business policy id (%s) is used in the type api, a valid state name must be supplied.
CAUSE: The state name was omitted.
ACTION: Specify a valid state name for the business policy object.
PARAMS: The parameter is the business policy object id that was supplied.

ERROR: [DM_API_E_WRONG_CACHE_NAME]

SEVERITY: ERROR
DESCRIPTION: S The global cache %s is not supported in flushglobalcache method.
CAUSE: The name of the global cache to be flushed is not supported in the flushglobalcache method.
ACTION: Currently, only user cache is allowed.
PARAMS:

ERROR: [DM_API_E_DYNAMIC_GROUP_UPDATE]

SEVERITY: ERROR
DESCRIPTION: The dynamic_groups field can be updated only by append and remove operations.
CAUSE: The session config field dynamic_groups is used to control the set of dynamic groups that the current session is involved in. Changing the set of dynamic groups is done by removing or appending groups from dynamic_groups list. The list does not allow manipulation by other operations: set, insert, truncate.
ACTION: Use the documented operations for manipulating the dynamic_groups list.
PARAMS:

ERROR: [DM_API_E_NOMESSAGE]

SEVERITY: ERROR
DESCRIPTION: S No messsage specified for routing.
CAUSE:
ACTION:
PARAMS: None.

ERROR: [DM_API_E_BADATTRNAME]

SEVERITY: ERROR
DESCRIPTION: S Bad attribute name %s for document/object.
CAUSE: An incorrect attribute name was supplied with the API command.
ACTION: Use a correct attribute name. Insure that no spaces have been placed between comma delimiters.
PARAMS: None.

ERROR: [DM_API_E_DOWNREV_SERVER_VER]

SEVERITY: ERROR
DESCRIPTION: SSSS The docbase (%s) has version (%s) which does not support the operation (%s). This operation requires a server of at least version (%s)
CAUSE: You can only connect to a docbase with a higher version.
ACTION:
PARAMS:

ERROR: [DM_API_E_SESSION_DISABLED]

SEVERITY: ERROR
DESCRIPTION: The session was disabled on an exception, only getmessage and disconnect are allowed on a disabled session.
CAUSE: An earlier error of type DM_API_E_EXCEPTION_ON_SESSION has been reported on this session.
ACTION: Use the disconnect command to end the session.
PARAMS:

ERROR: [DM_API_E_MISSING_CONTAINMENT_DESC]

SEVERITY: ERROR
DESCRIPTION: S A containment type of %s was supplied but its corresponding containment description is missing.
CAUSE: The containment description must be supplied if the containment type is supplied.
ACTION: Supply the corresponding containment description.
PARAMS:

ERROR: [DM_API_E_INVALID_PERMIT_TYPE]

SEVERITY: ERROR
DESCRIPTION: S An unrecognized permit_type value of %s was specified. Please check the value and try again.
CAUSE: An unrecognized value for permit_type was specified.
ACTION: Check the value supplied for permit_type and retry the API statement.
PARAMS:

ERROR: [DM_API_E_OPERATION_UNSUPPORTED]

SEVERITY: ERROR
DESCRIPTION: SS This %s operation cannot be performed because the server does not support the %s method. There is an incompatibility between your client library (DMCL) and the current Documentum server.
CAUSE: The server to which the application is connected does not support a method call used by the DMCL in the current command. The application is likely connected to an older server which cannot process the requested action.
ACTION: If possible upgrade the server to resolve the problem.
PARAMS: The command as specified and the unsupported METHOD call.

ERROR: [DM_API_E_NO_SERVERMAP]

SEVERITY: ERROR
DESCRIPTION: No server map information from docbroker.
CAUSE: The docbroker is not running or the server is not running
ACTION: Check with your dmadmin for help
PARAMS:

ERROR: [DM_API_E_BADQUEUE]

SEVERITY: ERROR
DESCRIPTION: No queue name has been given.
CAUSE: You have issued a dequeue command without specifying a queue name.
ACTION: Correct the command line to include the queue name.
PARAMS: None.

ERROR: [DM_API_E_POSITIONAL_PARAM_MISSING]

SEVERITY: ERROR
DESCRIPTION: IS The required positional parameter, %d, was not supplied. Please provide a value for %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_E_NO_SESSION]

SEVERITY: ERROR
DESCRIPTION: There are no more available sessions.
CAUSE: User has used all available sessions. Current limit is 10 per application.
ACTION: Close some unused sessions in your application.
PARAMS:

ERROR: [DM_API_E_MISS_STATE_POS]

SEVERITY: ERROR
DESCRIPTION: The movestate API requires both old and new positions be specified.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_API_W_NO_VALUE]

SEVERITY: WARNING
DESCRIPTION: S There are no values in the repeating attribute %s.
CAUSE: You have requested a value from the repeating attribute, but no values have been set for this attribute. The _count value for this attribute is zero.
ACTION: None required. This message is informational. In general, the repeating attributes _count value should be checked before values are requested. _count tells you how many values the repeating attribute contains, so that you can retrieve all of them.
PARAMS:

ERROR: [DM_API_W_NO_MATCH]

SEVERITY: WARNING
DESCRIPTION: S There was no match in the docbase for the qualification: %s
CAUSE: The qualification you provided did not match any object.
ACTION: None required. If you think there really should have been a match reexamine your qualification, correct it, and resubmit it.
PARAMS: The qualification.

ERROR: [DM_API_W_CACHE_FLUSH]

SEVERITY: WARNING
DESCRIPTION: Unable to flush query cache.
CAUSE: Query caching is disabled for your session or docbase. Unable to flush the cache.
ACTION: Query caching must be enabled, either by your System Administrator setting the effective_date in the Docbase Config, or through your dmcl.ini.
PARAMS:

ERROR: [DM_API_W_SERVER_NEED_RESTART]

SEVERITY: WARNING
DESCRIPTION: S Changes made by the apply method %s will not take effect until Content Server is restarted.
CAUSE: Content server needs to restart after certain APPLY method being executed. Such apply method includes only DEFAULT_RETENTION_ATTR for now.
ACTION: An Admin user needs to restart the content server.
PARAMS:

ERROR: [DM_API_W_EXTRA_PARAMETER]

SEVERITY: WARNING
DESCRIPTION: S The extra parameter, %s, is only allowed for date attribute.
CAUSE: You have provided an extra parameter in the Set, Append, Insert API for non-date attribute.
ACTION: Remove the extra parameter.
PARAMS:

ERROR: [DM_API_W_OLDTYPE]

SEVERITY: WARNING
DESCRIPTION: S Type name %s should no longer be used in the creation of objects.
CAUSE: An old type has been used document, cabinet, folder.
ACTION: In the future, use dm_document, dm_cabinet, dm_folder.
PARAMS: None.

ERROR: [DM_API_W_CONTAINMENT_FEATURES_NOT_SUPPORTED]

SEVERITY: WARNING
DESCRIPTION: SSSS The docbase (%s) has version (%s) which does not support setting containment_type and containment_desc attributes in the operation (%s). These features require a server of at least version (%s)
CAUSE: You can only set containment_type and containment_desc attributes in a 4.1 or later server
ACTION: Use a newer server if you wish to set the containment_type and containment_desc attributes.
PARAMS: docbase, old server version, api operation, minimum server version required.

ERROR: [DM_API_I_OPTION_USAGE]

SEVERITY: INFORMATION
DESCRIPTION: SS This option is currently (%s). You need system administrators privilege to turn on -o flags. You can turn on[/off] this option by issueing an api command: apply,,NULL,SET_OPTIONS,OPTION,S,%s, VALUE,B,T[/F]
CAUSE: Instruction to turn on/off -o option
ACTION: None.
PARAMS:

ERROR: [DM_API_I_SPECIAL_FACILITY_USAGE]

SEVERITY: INFORMATION
DESCRIPTION: S You can turn on/off (%s) trace facility by issueing an api command:apply,c,NULL,MODIFY_TRACE,SYBSYSTEM,S,fulltext,VALUE,S,{all,document,verity,none}
CAUSE: Instruction to turn on trace for this facility on the server side
ACTION: None.
PARAMS:

ERROR: [DM_API_I_FACILITY_USAGE]

SEVERITY: INFORMATION
DESCRIPTION: SS You can turn on (%s) trace facility by issueing an api command:trace,,,apilogfile,%s. You can turn off this facility by using the same api with severity_level set to 0.
CAUSE: Instruction to turn on trace for this facility on the server side
ACTION: None.
PARAMS:

ERROR: [DM_API_I_FACILITY_NOT_AVAILABLE]

SEVERITY: INFORMATION
DESCRIPTION: S Current facility (%s) does not have trace
CAUSE: the information of the facility
ACTION: None.
PARAMS:

ERROR: [DM_API_I_SQL_TRACE_USAGE]

SEVERITY: INFORMATION
DESCRIPTION: S SQL Trace is currently (%s). The api command to turn on[/off] SQL trace is: trace,,1[/0],,SQL_TRACE
CAUSE: this is the instruction for session based sql trace.
ACTION: none.
PARAMS:

Advertisements

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: