Initial steps and commands
BMC Support might ask that you perform steps similar to the following.
- Run mqsexport to export the profile containing the model exhibiting the issue, as shown in the following example:
mqsexport –p BMCSOFTWARE -–profile Profile0 Profile0.zip SA - Export the transactions exhibiting the issue. You can specify the mask option which replaces as much of your data as possible with a non-descript replacement. However, if you have payload filters on specific data this might fail to cause the same results as a real transaction.
- One specific transaction: resolver -u SA -p BMCSOFTWARE export all Profile0 Model0_1 1234
- Sampling of transactions: resolver –u SA –p BMCSOFTWARE export_range all Profile0 Model0_1 now-300 now 50 "d:/TxnExports/" true
- Replay a transaction to verify the issue can be replicated using this procedure.
resolver –u SA –p BMCSOFTWARE replay d:/TxnExports/1234 10000 1 1 30000 300 - Capture screen shots of the issue.
- Zip up the profile and transaction export files and any screenshots for BMC Support Analysis.
Commands and syntax
The resolver utility command has the following syntax:
The following commands are supported:
The following table lists the required and optional parameters for the resolver utility.
Option | Argument | Description |
|---|---|---|
-h | Host | Host:Port | The host and optionally the port of the Application Service. This is optional when running on the same machine as the installation which would be the normal case. |
-u | User | A user id able to log into the TMTM product. Required. |
-p | Password | The password for the user id specified; either –p or –s is required. |
-s | Password | Specifies the password for the user id specified is specified via stdin; either –p or –s is required. |
-k | Skew | Milliseconds to skew the publish times when replaying a transaction. |