5.3.1 Setting Replay Definition Attributes
You can edit the replay definition attributes.
The following table lists replay definition attributes.
Table 5-1 Replay Definition Attributes
| Attribute | Description | Default Value | Editable |
|---|---|---|---|
| name | Replay definition name | - | yes |
| Tuxedo user name | The Tuxedo user name used to do tpinit() |
- | yes |
| Tuxedo client name | The Tuxedo client name used to do tpinit() |
- | yes |
| Tuxedo group name | The Tuxedo client name used to do tpinit() |
- | yes |
| transaction calls | Call tpbegin()when starting the call(s), and call tpcommit() when ending the calls
|
From source call path metrics | yes |
| transaction parameters | Call tpbegin() when starting the call(s), and call tpcommit() when ending the calls
|
From source XA metrics | no |
| break when any call fails | Whether to break when any call fails. Its value is yes or no. | - | yes |
| create time | The time when the definition was created | - | no |
| modify time | The time when the definition was modified | - | no |
The default service call attributes are from the first called service (not the "Initial Called Service" in the call path when the initiator is a server) when the replay definition is constructed from call path metrics. The following table lists service calls attributes of replay definition.
Table 5-2 Replay Definition Service Calls Attributes
| Attribute | Default Value | Editable |
|---|---|---|
| service name | From source metrics | No |
| source correlation ID | From source metrics | No |
| call flag "TPNOTRAN" | From the source metrics | Yes |
| call flag "TPNOCHANGE" | From the source metrics | Yes |
| call flag "TPNOCOPY" | From the source metrics | Yes |
| call flag "TPNOBLOCK" | From the source metrics | Yes |
| call flag "TPNOTIME" | From the source metrics | Yes |
| call flag "TPSIGRSTRT" | From the source metrics | Yes |
Parent topic: Creating a Replay Definition