Question & Answer
Question
Collecting troubleshooting data documents aid in problem determination and save time resolving Problem Cases (previously called PMRs).
Answer
Collecting troubleshooting data early, even before opening the Case, helps IBM® Support quickly determine whether:
Symptoms match known problems (rediscovery).
There is a non-defect problem that can be identified and resolved.
There is a defect that identifies a workaround to reduce severity.
Locating root cause can speed development of a code fix.
Symptoms match known problems (rediscovery).
There is a non-defect problem that can be identified and resolved.
There is a defect that identifies a workaround to reduce severity.
Locating root cause can speed development of a code fix.
Collecting Data: Table of contents:
 |
Gathering general information |
 |
Gathering Replication Process Information |
 |
Submitting Information to IBM Support |
 |
Online Self-Help Resources |
 |
Related Information |
| Gathering General Information |
From both source and target server:
From a Spectrum Protect Administrative command-line client (DSMADMC), enter the following commands:
- QUERY SYSTEM > querysys.out
- QUERY NODE f=d
- QUERY ACTLOG begind=<mm/dd/yyyy> begint=<hh:mm> endd=<mm/dd/yyyy> endt=<hh:mm> > actlog.out
- - where begind and begint are the beginning date and time for the actlog entries being collected
- where endd and endt are the ending date and time for the actlog entries being collected
- the actlog gather should cover the full-timeframe of the issue being diagnosed
Explicitly using these commands will redirect the output to files called querysys.out and actlog.out in the Spectrum Protect server working directory. The names of these files can be changed and a full path can be specified to place the output in any wanted directory that uses any wanted name.
The mentioned files along with the following files should be included as general information:
- dsmffdc.log.x files (located in the instance directory)
- dsmserv.opt
Capture a trace of the replication process failure with the following IBM Spectrum Protect server administrative commands on both the source and target servers :
- trace disable *
- trace enable REPL
- trace begin <filename> ...where filename is a full path file name to write trace data
<Re-create the issue here, run replication and wait until it fails>
- trace flush
- trace end
- trace disable *
Also, the output from the following IBM Spectrum Protect server administrative commands will be needed from the source server :
- QUERY REPLRULE
- QUERY REPLFAILURES
- VALIDATE REPLPOLICY
- QUERY REPLNODE *
- QUERY REPLICATION <node_name>
- QUERY REPLSERVER
| Submitting Information to IBM Support |
After a Case is open, you can submit diagnostic troubleshooting data to IBM.
When data is uploaded to the Case, the status will be automatically be updated to acknowledge that data has been received. If you are still working with older Problem Management Records, you will want to update the PMR to indicate that you have sent the data.
| Online Self-Help Resources |
-
Review up-to-date product information at the IBM Spectrum Protect page.
-
Sign into your account on the Spectrum Protect Product page, to access additional resources or to open a Case with the Support team.
| Related Information |
[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEQVQ","label":"IBM Spectrum Protect"},"ARM Category":[{"code":"a8m50000000Ci5XAAS","label":"Server"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
05 February 2021
UID
ibm16339755