DSRUTIL -C status - Return Status and Codes
For legacy purposes,
RPREPL was superseded by
DSRUTIL DSRUTIL Return Status:
1xxx ; Source database
2xxx ; Source database for a named agent
3xxx ; Target database
Where:
xxx == Group Status Code Numbers:
| 100 | CONNECTING |
| 101 | PROCESSING |
| 102 | STALLED |
| 103 | PRE_TRANSITION |
| 104 | LISTENING |
| 105 | TRANSITION |
| 199 | INACTIVE |
| 255 | UNKNOWN |
Example: When Replication is operating normally:
| 1101 | DSRUTIL source -C status |
| 2101 | DSRUTIL source -C status agent1 |
| 3101 | DSRUTIL target -C status |
Return Status for:
DSRUTIL -C status -detailOpenEdge 10.1A introduced granular detail status codes per group which are returned when the
-detail argument is used with:
DSRUTIL/rprepl -C status [-detail]
Sometime later in OpenEdge 11, the
-verbose argument makes deciphering these return codes a whole lot easier.
A DOC BUG CONT-4825 was raised for the following, which is ambiguous and open to interpretation with respect to context .
"A query on the source produces a resulting value that is 1xxx or 6xxx. A query on the target produces a value that is 2xxx or 3xxx" .
Example: DSRUTIL Return Codes
| 6021; Server Normal Processing | DSRUTIL source -C status -detail |
| 3049; Agent Normal Processing | DSRUTIL source -C status agent1 -detail |
| 1063; Agent is Ended | DSRUTIL source -C status agent2 -detail |
Additionally the DSRUTIL Tables Detail and Verbose vs Status return code Tables are confusing. The following Article seeks to de-obsfucate the mysteries of
DSRUTIL STATUS vs -detail 
