How To
Summary
Question:
Why is it important to collect troubleshooting data for Object Storage issues in IBM Storage Protect?
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.
Objective
Collecting Data: Table of contents:Object StorageGathering General Information:
Entering general information into an electronically-opened Problem Case (previously called PMRs) eliminates waiting on the phone to provide general information to support
From the Storage Protect Server Admin command line client (dsmadmc), enter the following commands:
SHOW TIME (date and time of SP server)
QUERY SYSTEM > querysys.out
QUERY ACTLOG begind=<mm/dd/yyyy> begint=<hh:mm> endd=<mm/dd/yyyy> endt=<hh:mm> > actlog.out
query server <OBJECTAGENT> f=d
query node <OBJECTCLIENT> f=d
- 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 Storage 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:
Include the command outputs listed above along with the following files and details:
The primary log file is protect.log, It is located inside the Object Agent's instance directory. Default Location of protect.log typically found under
/tsm/tsminst1/<object-name><object>.config file located under the instance path:
/tsm/tsminst1/<object-name>Run the following command to locate the running Object Agent process and share the output
ps -ef | grep spObjectAgentEnabling Debug Mode for Object Agent: The Debug logs are essential when troubleshooting failures, hangs, or unexpected object agent behavior. Please share the debug logs using below step
Step 1: Go to the Object Agent instance directory
/tsm/tsminst1/<object-name>, Then Edit the object_agent_config.json to enable debug mode. Modify debugMode to true in the log section as below "log": { "logSize": 500, "logAge": 10, "logBackups": 4, "debugMode": true } Save the file.Step 2: Reproduce the operation Run the backup/restore item list operation that is failing. This will generate detailed debug logs in the same instance directory path as like protect.log file
dsmffdc.log.x files (located in the instance directory and covering the issue timeframe)
IBM Storage Protect Server version (for example: 8.1.0.0)
Operating System name and version (for example: Red Hat Enterprise Linux 7.1)
System architecture (for example: x86_64)
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 Storage Protect page.
Sign into your account on the Storage Protect Product page, to access additional resources or to open a Case with the Support team.
Environment
All Environment
Related Information
Document Location
Worldwide
Historical Number
TS020719577
Product Synonym
TSM;Tivoli Storage Manager;Spectrum Protect;Storage Protect;ISP,Object Storage;Object Agent;Storage protect plus
Was this topic helpful?
Document Information
Modified date:
27 January 2026
UID
ibm17256873