How To
Summary
Initial MustGather documentation guide
Objective
Steps
- Operating System Type and Version.
- Product Name and Version.
- What are you trying to do and what is the result?
- Is this time the first time this problem occurred?
- What changed since the activity last worked?
- Has the problem occurred only once or it’s easily recreatable?
- Is the problem in the Configuration Tool? If yes, what type of Configuration Tool do you use? z/OSMF or Liberty?
- Which Data Streams are used?
- Which type of Subscribers are used?
- Screen captures of the problem if applicable.
Upload these files if available:
- System Data Engine (SDE): HBOSMF job log
- Log Forwarder (LF): HBOPROC job log
- Data Streamer (DS): HBODSPRO job log
- A complete unformatted DUMP if there is an Abend
- The SYSLOG at time of error
- policyname.policy
- policyname.layout
- policyname.sde
- policyname.zlf.conf
- policyname.config.properties
- TAR the config directory from OMVS.
Example: tar -czf TS003010487.tar.gz -C /u/root/cdpConfig
- Transfer the files using the info here
Depending on the components that are installed in your environment, the Collect logs option collects the logs for the Problem Insight server.
All collected logs are stored in the archive file izoa-support-logs.TIMESTAMP.zip, where TIMESTAMP has the format YYYY-MM-DD_HH:MM:SS. The log archive is stored in the directory that is specified by the value of the TMPDIR environment variable. If this variable is not set, the /tmp directory is used. If the /tmp directory cannot be written to, the HOME directory for the user is used.
Gathering logs after distributed version 5.1.10
For gathering ZLDA logs that run as docker or podman containers under Linux after 5.1.10 you can run the following command:
cd <ZOA_HOME>
./bin/dockerManageZoa.sh gather
Please follow this link for more information regarding dockerManageZoa.sh commands.
Document Location
Worldwide
Product Synonym
zLDA; Z Log and Data Analytics; IBM Z Operational Log and Data Analytics
Was this topic helpful?
Document Information
Modified date:
28 August 2026
UID
ibm17176664