Question & Answer
Question
There are 4 different options in the "Download Support package" page in the GUI. Which one should you use, when, and why?
Answer
Below are the 4 options that the GUI provides, and an approximate size for a bundle from a system with a small number of volumes.
| Option | Description | ||
| 1 | Standard logs | ||
| 2 | Standard logs plus one existing statesave | ||
| 3 | Standard logs plus most recent statesave from each node. i.e. the statesave is from around the time when the issue occurred | ||
| 4 | Standard logs plus new statesaves. i.e. a new statesave is generated at the time the option is selected and overwrites any old state saves |
What to consider when collecting logs
Two major factors play a part in deciding which logs to send to IBM when opening a problem ticket:
1. Speed
2. Being asked for more logs in the future.
There is no question that collection Option 1 will be much faster than Option 4. Option 1 will be generated more rapidly, and it will be much smaller, so it will be quicker to upload it to IBM. However Option 4 gives the greatest chance that the correct data will be uploaded on the first attempt.
It is also worth being aware that not collecting livedumps (Option 4) soon after the problem may reduce the likelihood that the livedump still contains the necessary data to diagnose the problem.
Glossary
- Statesave - The term statesave is used to mean either a dump or a livedump
- Livedump - A livedump is a binary data capture that collects the current state of the software with minimal impact to I/O operations. The contents of a livedump are similar to the contents of a dump
- Dump - A dump file is collected when the software restarts for some reason. It is similar in nature to a core file, and can be used to understand why the software restarted
Was this topic helpful?
Document Information
Modified date:
17 February 2023
UID
ssg1S1008039