Understand DSRUTIL STATUS vs -detail (or verbose) return codes
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
When performing specific OpenEdge Replication server, OpenEdge Replication agent, source database, and target database requests with the DSRUTIL utility it is important to understand the differences in return codes.
When you use the command:
dsrutil dbname -C status, only the
status codes are returned. These are essentially a per-fixed group status
code. For
example:1101 : DSRUTIL source -C status
2101 : DSRUTIL source -C status agent1
3101 : DSRUTIL target -C statusWhen
dsrutil dbname -C status -detail (or verbose) is used, only the
detail status codes are returned, which are a sub-set of the group status'.
For
example:6021 : DSRUTIL source -C status -detail
3049 : DSRUTIL source -C status agent1 -detail
1063 : DSRUTIL source -C status agent2 -detailIt is important to understand the difference between these two sets (a set and a sub-set)
as together they provide a fuller picture of the replication total status. For example,
the status group 101 Processing in the previous example provides a
finer granularity of what processing is taking place. For example:
- RPLS 6005 | RPLA 3048 Startup Synchronization
- RPLS 6021 | RPLA 3049 Normal Processing
- RPLS 6004 | RPLA 3050 Recovery Synchronization
The following list provides this detail grouped by focus, source, target, or source to
agent). Using DSRUTIL -C status verbose provides both the status
code and description to record status pages.
Server to Agent initial connect status codes
| Status | Description |
|---|---|
| 1001 | Initial Connection |
| 1002 | Initializing |
| 1003 | Target in Quiet Point |
| 1032 | Initial Connection Failed |
| 1033 | Recovery Failed |
| 1034 | Invalid Target Database Configuration |
| 1035 | Agent Failed |
| 1036 | Agent is Ignored |
| 1037 | Agent is Stopped |
| 1038 | Agent is Terminated |
| 1063 | Agent is Ended |
Replication Server
| Status | Description |
|---|---|
| 1100 | Connecting status |
| 1101 | Processing status |
| 1102 | Stalled status |
| 1103 | Pre-transition status |
| 1104 | Listening status |
| 1105 | Transition status |
| 1199 | Inactive |
| 1255 | Unknown |
| 6001 | Server Initialisation |
| 6002 | Connecting to Agent(s) |
| 6003 | Configuring Agent(s) |
| 6004 | Recovery Processing |
| 6005 | Startup Synchronization |
| 6006 | Initiating Agent to Agent Connections |
| 6021 | Normal Processing |
| 6022 | Performing Transition |
| 6060 | Server is ended |
Control Agent
| Status | Description |
|---|---|
| 2100 | Connecting status |
| 2101 | Processing status |
| 2102 | Stalled status |
| 2103 | Pre-transition status |
| 2104 | Listening status |
| 2105 | Transition status |
| 2080 | Pre-transition |
| 2081 | Applying After-image Extent |
| 2082 | Transitioning |
| 2083 | Listening |
| 2199 | Inactive |
| 2255 | Unknown |
Agent
| Status | description |
|---|---|
| 3100 | Connecting status |
| 3101 | Processing status |
| 3102 | Stalled status |
| 3103 | Pre-transition status |
| 3104 | Listening status |
| 3105 | Transition status |
| 3048 | Startup Synchronization |
| 3049 | Normal Processing |
| 3050 | Recovery Synchronization |
| 3051 | Being Transitioned |
| 3052 | Target Database in Quiet Point |
| 3053 | Target Database is in a BI stall |
| 3054 | Target Database is in an AI stall |
| 3055 | Online backup of Target Database |
| 3199 | Inactive |
| 3255 | Unknown |
Example
Here are some examples of status before connection:
|
|
Then when connected:
|
|