|
msiDataObjPutWithOptions |
( |
msParam_t * |
inpParam1, |
|
|
msParam_t * |
inpParam2, |
|
|
msParam_t * |
inpParam3, |
|
|
msParam_t * |
inpOverwriteParam, |
|
|
msParam_t * |
inpAllCopiesParam, |
|
|
msParam_t * |
outParam, |
|
|
ruleExecInfo_t * |
rei | |
|
) |
| | |
- Description:
- This microservice requests the client to call a rcDataObjPut API as part of a workflow execution, with options.
- Deprecated:
- Since 2.2, msiDataObjPut can take a parameter with key-values format which make this microservice obsolete.
- Module:
- core
- Since:
- pre-2.1
- Author:
- Romain Guinot
- Date:
- 2008
- Note:
- This microservice requests the client to call a rcDataObjPut API as part of a workflow execution, with options.
- Example Usage:
- See clients/icommands/test/rules3.0/
- Parameters:
-
[in] | inpParam1 | - a DataObjInp_MS_T or a STR_MS_T which would be taken as dataObj path. |
[in] | inpParam2 | - Optional - a STR_MS_T which specifies the resource. |
[in] | inpParam3 | - Optional - a STR_MS_T which specifies the client's local file path. |
[in] | inpOverwriteParam | - Optional - a STR_MS_T which specifies if the put should do an overwrite if content already exists in the resource. To trigger an overwrite, "forceFlag" keyword is expected |
[in] | inpAllCopiesParam | - Optional - a STR_MS_T which specifies if that in case of an overwrite,the operation should overwrite all existing copies |
[out] | outParam | - a INT_MS_T containing the status. |
[in,out] | rei | - The RuleExecInfo structure that is automatically handled by the rule engine. The user does not include rei as a parameter in the rule invocation. |
- Session Variables Used:
- none
- Session Variables Modified:
- none
- iCAT Attributes Used:
- none
- iCAT Attributes Modified:
- none
- Side Effect:
- none
- Returns:
- integer
- Return values:
-
- Precondition:
- none
- Postcondition:
- none
- See also:
- none
Definition at line 3259 of file reDataObjOpr.c.
|