Troubleshooting
Problem
This document contains information about how to perform an IBM i partition main storage dump (MSD). This document covers the HMC graphical user interfaces for: Version 8 "enhanced"; Version 8 "classic" and Version 7; Version 6 and earlier.
Resolving The Problem
PLEASE FULLY READ THIS SECTION FIRST
Forcing a MSD generally means that the system is not detecting a problem, and that to recover and collect diagnostic data forcing a MSD is necessary. Problems of this sort frequently involve data or tasks that have not run in a long time. This could mean that data, necessary to understand the problem, is no longer in memory. It is important to attempt to bring data back into memory shortly BEFORE forcing the MSD.
If access to the partition is still possible, it is recommended to log into SST and run Advanced Analysis macro: servicedocs to Spoolfile. While IBM can use the servicedocs output, the important aspect is that it pulls task and wait related data back into memory.
1. STRSST and sign in
2. Option 1. Start a service tool
3. Option 4. Display/Alter/Dump
4. Option 2. Dump to printer
5. Option 2. Licensed Internal Code (LIC) data
6. Option 14. Advanced analysis
7. Enter the following data:
1 servicedocs
Press Enter
8. Press Enter on the blank Options line
9. Enter the following data:
Dump title . . . . . . . . . . . Servicedocs
Press Enter
2. Option 1. Start a service tool
3. Option 4. Display/Alter/Dump
4. Option 2. Dump to printer
5. Option 2. Licensed Internal Code (LIC) data
6. Option 14. Advanced analysis
7. Enter the following data:
1 servicedocs
Press Enter
8. Press Enter on the blank Options line
9. Enter the following data:
Dump title . . . . . . . . . . . Servicedocs
Press Enter
If access to the partition is not possible (perhaps due to the reason that the MSD is being performed), we can attempt to run a similar function by sending the Function 21 (Force DST) twice (within 5 minutes) to the partition from the HMC.
From the server's All Partitions view, click on the specific partition name. Once that displays, in the left navigation, select Serviceability. It the main window, select "(21) Activate Dedicated Service Tools". After it posts a dialog 'Operator panel function 21 initiated.', hit Ok. Wait 30 seconds, and then select "(21) Activate Dedicated Service Tools" one more time.
After one of the two actions above is performed, proceed directly to the MSD process below.
HMC Version 8+ "enhanced" UI
1. In the navigation area click Resources > All Partitions.
2. Select the partition to perform the MSD on, click Actions > Restart...
Alternate: From the the partition's General Properties panel view, select Partition Actions > Operations > Restart
3. Select restart type of Dump and click ok.
Note: This task can target more than one partition. Ensure only the partition(s) to be dumped are selected.
Ensure Dump is selected, and click OK. At this time, the partition goes through MSD processing.
4. Copy dump to ASP
Depending on the autocopy settings, the dump may need to be manually copied to ASP. To manually copy the partition MSD to ASP, do the following:
From the Main Storage Dump Occurred screen, do the following:
1 | Press the Enter key to copy the MSD for service or view the MSD. |
2 | Select Work with current main storage dump (MSD) (Option 1). |
3 | Select Copy to ASP (Option 3). |
4 | Give your MSD a name. We recommend the IBM problem number and date/time. Press the Enter key. |
5 | The Copy Main Storage Dump to System ASP Status screen is shown. The copy begins when a condition known as full paging is reached. IBM does not recommend that you use the options to cancel or return and continue copy without direction from IBM Support. |
6 | Once full paging is reached, the Main Storage Dump completion status is shown. |
7 | When the copy is complete, you are shown the message Copy completed normally at the bottom of the screen. |
8 | On the console for the failed partition (the one for which the MSD was forced), press F3 two times to start an IPL. The partition will power down and start an IPL. |
HMC Version 7 and Version 8 "classic" UI
1. In the navigation area, expand Systems Management > Servers and select the target server
2. In the work area, select the partition to perform the MSD on then click Operations > Restart
3. Choose Dump and click OK.
Note: This task can target more than one partition. Ensure only the partition(s) to be dumped are listed.
Ensure Dump is selected, and click OK. At this time, the partition goes through MSD processing.
4. Copy the dump to ASP
Depending on the autocopy settings, the dump may need to be manually copied to ASP. To manually copy the partition MSD to ASP, do the following:
From the Main Storage Dump Occurred screen, do the following:
1 | Press the Enter key to copy the MSD for service or view the MSD. |
2 | Select Work with current main storage dump (MSD) (Option 1). |
3 | Select Copy to ASP (Option 3). |
4 | Give your MSD a name. We recommend the IBM problem number and date/time. Press the Enter key. |
5 | The Copy Main Storage Dump to System ASP Status screen is shown. The copy begins when a condition known as full paging is reached. IBM does not recommend that you use the options to cancel or return and continue copy without direction from IBM Support. |
6 | Once full paging is reached, the Main Storage Dump completion status is shown. |
7 | When the copy is complete, you are shown the message Copy completed normally at the bottom of the screen. |
8 | On the console for the failed partition (the one for which the MSD was forced), press F3 two times to start an IPL. The partition will power down and start an IPL. |
1. In the navigation area, expand Systems Management > Servers and select the target server
2. In the work area, select the partition to perform the MSD on then click Operations > Restart
2. Choose Dump and click OK.
[{"Product":{"code":"SSB6AA","label":"Power System Hardware Management Console Physical Appliance"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"HMC","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"5.4.0;5.4.5;6.1.0;6.1.1","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]
Historical Number
352502251
Was this topic helpful?
Document Information
Modified date:
22 September 2021
UID
nas8N1015896