Difference between revisions of "Bop odump"
From SDU
(New page: == Usage == pdm_odump <domsrvr_name> <object_factory> <where_clause> [attributes] <br> {| |- ! Parameter ! Description ! Remarks |- | <domsrvr_name> | the name of the object engine that is...) |
|||
| Line 33: | Line 33: | ||
bop_odmp domsrvr cr "" ref_num | bop_odmp domsrvr cr "" ref_num | ||
| − | * Dump all | + | * Dump all Incidents attached to Problem 12 and still active |
| − | bop_odump domsrvr | + | bop_odump domsrvr in " problem.ref_num='12' AND active=1 " |
* Dump all Requests that belong to an Analyst with the username Fred, show only the close date | * Dump all Requests that belong to an Analyst with the username Fred, show only the close date | ||
Revision as of 20:03, 11 February 2008
Usage
pdm_odump <domsrvr_name> <object_factory> <where_clause> [attributes]
| Parameter | Description | Remarks | |
|---|---|---|---|
| <domsrvr_name> | the name of the object engine that is interrogated. | required - usually this is simply domsrvr | |
| <object_factory> | the name of the object that you want to dump | required for example 'cr', 'chg', 'alg', 'nr' | |
| <where_clause> | additional filter for the list, has the form of an SQL 'where' clause | required - just put "" for an empty clause | |
| [attributes] | list of attributes of the object to return from the search | the list of attributes is space separated. |
Examples
- Dump the Reference number for all Requests
bop_odmp domsrvr cr "" ref_num
- Dump all Incidents attached to Problem 12 and still active
bop_odump domsrvr in " problem.ref_num='12' AND active=1 "
- Dump all Requests that belong to an Analyst with the username Fred, show only the close date
bop_odump domsrvr cr " assignee.userid='fred' " close_date
To make corrections or additions to this article, select the edit tab above.
To discuss or ask questions about this article, select the discussion tab above.
To discuss or ask questions about this article, select the discussion tab above.
