Troubleshooting
Problem
This document describes how to force a Main Storage Dump (MSD) on a stand-alone system when the system is hung.
Resolving The Problem
This document provides instructions on how to force a Main Storage Dump (MSD) on a stand-alone system when the system is hung or in a loop.
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. 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 DST. Put the system in manual mode using the front panel, and enter Function 21.
|
1. |
Put the system in manual mode:
- Use front panel to go up to 02, and press Enter - Press Enter again to get to the N
- Use up arrow to change to M, and press Enter - Press Enter until you get 02 alone - Then down to 01 and press Enter (display shows 01 B M) |
| 2. |
Force the dump:
- Use front panel and go up to 22; press Enter. - System responds with A1003022 to verify the action - Use the up or down arrow, select 22 again, and press Enter Note: With Power 10 systems, when you go to function 22 to get the A1003022 you no longer have to up and down arrow to hit 22 again. You just need to press the enter button again at A1003022 for the MSD IPL to proceed.
The system should respond with a number of System Reference Codes, all beginning with D1. If not, call for support before continuing. |
| 3. | Once the MSD IPL completes, the console will display a screen titled either Main Storage Dump Manager or Main Storage Dump Occurred (depending upon system release). Press the Enter key. |
| 4. | Select Option 1, Work with current main storage dump, and press the Enter key. |
| 5. | Select the option to Copy to ASP. Note: You may get a message saying auto copy is in progress; if so, press F5 or wait until it is complete, and skip down to Step 9, otherwise, continue with Step 6. |
| 6. | Name the MSD. IBM recommends the Case number and date/time. Press the Enter key. |
| 7. | 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. (Prior to reaching full paging, the partition will display SRCC6004250 or SRCC6004260 on the control panel.) |
| 8. | Once full paging is reached, the Main Storage Dump completion status is shown. |
| 9. | When the copy is complete, you are shown the message Copy completed normally at the bottom of the screen. |
| 10. | From the control panel, return the system to normal mode: - Use front panel to go up to 02, and press Enter - Press Enter again to get to the M - Use up arrow to change to N, and press Enter - Press Enter until you get 02 alone - Then down to 01 and press Enter (display will show 01 B N ) |
| 11. | On the console for the system (the one for which the MSD was forced), press F3 two times to start an IPL. The partition will power down and start an unattended IPL (if the mode was changed to normal). |
Once the system is back up and running, upload the MSD to ecurep: QMGTOOLS - MSD steps for customers: http://www.ibm.com/support/docview.wss?uid=nas8N1022171
[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000C4BAAU","label":"IBM i"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"6.1.0;7.1.0;7.2.0;7.3.0;7.4.0;7.5.0;and future releases"},{"Product":{"code":"SSC3X7","label":"IBM i 6.1"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":" ","Platform":[{"code":"","label":null}],"Version":"","Edition":"","Line of Business":{"code":"","label":""}},{"Product":{"code":"SSC52E","label":"IBM i 7.1 Preventative Service Planning"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":" ","Platform":[{"code":"","label":null}],"Version":"","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}},{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSB23CE","label":"IBM i 7.5 Preventative Service Planning"},"ARM Category":[{"code":"a8m0z0000000C4BAAU","label":"IBM i"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Historical Number
533143458
Was this topic helpful?
Document Information
Modified date:
10 December 2024
UID
nas8N1012799