This section discusses using MPE/iX and initial system loader commands,
options, and utilities to dump system memory and secondary storage to tape.
What is the Function of the DUMP Utility?
The DUMP utility saves the current state of the system's
main memory and secondary storage to tape for later analysis. Perform
a memory dump after a system failure or hang, for a recurring system
problem, or when the system fails to boot properly. Have the tape
analyzed by your Hewlett-Packard Representative or your Hewlett-Packard
Response Center.
Using the DUMP Utility and Options
The DUMP utility has one basic option, SUBSET=ALL/MEMORY.
Because START/NOSTART are also options, DUMP can use several
START command options:
To perform a complete memory dump, enter the DUMP command. The
SUBSET=ALL option is the default option and dumps both main
and virtual memory. The SUBSET=MEMORY option is required to dump main
memory contents
only.
Issuing the command DUMP without any options
ISL> DUMP
is the same as specifying the following default options:
The DUMP command and its default options instruct the system to
perform the following tasks if an autoboot file exists, the autoboot
file is enabled, and the START option is specified:
Dump all memory and disk-based system data to tape.
Boot the system from disk after the dump is completed.
Boot with the configuration group CONFIG.SYS.
Log on in the user OPERATOR.SYS. (If there is no
OPERATOR.SYS user, you will see the MPE prompt).
Allow access to all mounted volumes by all users.
Restart jobs that are intact.
Entering the DUMP Utility and Starting the System
A procedure for performing a dump and booting a system includes
the following steps:
Mount a tape on the tape drive.
Soft reset the system using the access port method, boot from the
primary path, and enter the DUMP command at the ISL prompt.
CAUTION: Do not issue the RS command from the console or push
the RESET button on the front panel. Hard resetting the system initiates a
destructive processor self-test that invalidates dump data.There will be a
one- to two-second delay between typing TC and getting the message
Processor Dependent Code (PDC) revision X.X. During this time no
keys should be pressed on the console.
NOTE: If you have a 99X system, you must transfer to
the service processor before you can soft reset the system.
CM> SP
The system prompts for a user identification string and for the
correct date and time shortly after receiving the DUMP
command. The user can enter up to 80 characters, which can later be
displayed by DAT when analyzing the dump. There is a 60-second
timeout on this prompt. Once a key is pushed on the console keyboard,
the timeout is aborted and a carriage return is required to continue
with the dump. If a key is not pushed within 60 seconds, the prompt
times out, and the dump proceeds with a blank user dump ID in the
label. If the date and time are correct, press Return at the
date prompt. If the date or the time are incorrect, respond as
requested with the correct date and time in 24-hour format.
NOTE: The DUMP procedure shown in Example 3-7 was performed
on an N-Class system. The procedure assumes that autoboot is enabled.
Make necessary adjustments to the procedure if autoboot is disabled
on your system. Sequences from other installations may vary.
Example 3-7 Dumping the System
GSP> tc
TC
Execution of this command irrecoverably halts all system processing and
I/O activity and restarts the computer system.
Type Y to confirm your intention to restart the system: (Y/[N]) y
y
-> SPU hardware was successfully reset.
GSP Host Name: csyprel18(csysas18)
GSP>
********** VIRTUAL FRONT PANEL **********
System Boot detected
*****************************************
LEDs: RUN ATTENTION FAULT REMOTE POWER ON
FLASH OFF ON ON
platform config 626F
processor test 1142
processor test 1100
. . .
memory config 7280
I/O test 8107
I/O test 8107
processor test 1142
platform test 612A
I/O config 8238
*****************************************
************* EARLY BOOT VFP ************
End of early boot detected
*****************************************
Firmware Version 21.32
Duplex Console IO Dependent Code (IODC) revision 1
------------------------------------------------------------------------------
(c) Copyright 1995-2000, Hewlett-Packard Company, All rights reserved
------------------------------------------------------------------------------
Processor Speed State CoProcessor State Cache Size
Number State Inst Data
--------- -------- --------------------- ----------------- ------------
1 540 MHz Active Functional 512 KB 1MB
3 Unknown Stopped:Deconfigured Unknown 512 KB 1MB
Central Bus Speed (in MHz) : 133
Available Memory : 2097152 KB
Good Memory Required : Not initialized. Defaults to 32 MB.
Primary boot path: 0/0/2/0.6
Alternate boot path: 0/0/1/0.6
Console path: 0/0/4/0.0
Keyboard path: 0/0/4/0.0
---- Main Menu ---------------------------------------------------------------
Command Description
------- -----------
BOot [PRI|ALT|<path>] Boot from specified path
PAth [PRI|ALT] [<path>] Display or modify a path
SEArch [DIsplay|IPL] [<path>] Search for boot devices
COnfiguration menu Displays or sets boot values
INformation menu Displays hardware information
SERvice menu Displays service commands
DIsplay Redisplay the current menu
HElp [<menu>|<command>] Display help for menu or command
RESET Restart the system
----
Main Menu: Enter command or menu > bo
Interact with IPL (Y, N, or Cancel)?> y
Booting...
Boot IO Dependent Code (IODC) revision 1
SOFT Booted.MMSAVE Version 2.5
DUMPAREA found, save main memory to disc
ISL loaded
ISL Revision A.00.43 Apr 12, 2000
ISL> dump
MPE/iX launch facility
Scanning PCI BUS 0 ++*..++..........................
Scanning PCI BUS 8 ................................
Scanning PCI BUS 10 *................................
Scanning PCI BUS 20 *................................
Scanning PCI BUS 28 +...............................
Scanning PCI BUS 40 ................................
Scanning PCI BUS 50 ................................
Scanning PCI BUS 60 *................................
Scanning PCI BUS 80 ................................
Scanning PCI BUS 90 ................................
Scanning PCI BUS A0 ................................
Scanning PCI BUS C0 +...............................
Scanning PCI BUS D0 ................................
Scanning PCI BUS E0 ................................
MPE/XL Dump Version A.05.16 - initialization
A subset main memory and system volume set dump was requested.
Enter user identification string for this dump (80 chars or less):
Initialize_genesis - Ver bld1: <<pci 2.1601>>
FRI, JAN 18, 2002, 5:03:40 PM (y/n)?
Initialize_genesis = Ready to configure I/O
[CDM]8 8 0 18
Initialize memory manager completed.
MPE/XL Dump Facility Version A.05.16
Performing dump to tape.
adding permanent file to dump
adding permanent file to dump
Determine pre-compression size of secondary storage for ldev1
99 Megabytes of transient objects will be dumped for this device
Tape compression enabled.
6250 BPI not supported on this tape drive
1600 BPI density set on tape drive
tape is ready
Begin dump of Processor Internal Memory.
Processor Internal Memory dump complete.
Begin dump of main memory.
177 Megabytes of main memory will be dumped
................................................................
Dump of memory save area complete.
................................................
................................................................
Main memory dump complete.
Begin dump of secondary storage for ldev1
adding permanent file to dump
adding permanent file to dump
99 Megabytes of transient objects will be dumped for this device
................................................................
....................................
Secondary storage dump for ldev1 complete.
Dump completed - autoboot in progress.
ISL>
CAUTION: If your system has failed with a HPMC it is recommended
that a system reset (RS command) be executed prior to restarting
the system.
Start the system. Enter the START command at the ISL
prompt
There are various options available with each utility, as shown below. These
options may be entered in any order and must be separated by a blank or a
semicolon. Keywords must be entered as shown.
During an UPDATE, this option specifies whether or not the
configuration data files on disk (CONFIG group), are replaced by
those on tape (CONFIG). If this option is not specified, the
default is NOCONFIG
GROUP= configname Default: GROUP =
CONFIG
When the system is booted with NORECOVERY, the group specified
after GROUP= is the source of configuration information. When
performing an UPDATE, INSTALL, or DUMP, this group
is only in effect if START is specified or defaulted. When a
START command is entered, the group specified (or defaulted) for it
overrides any previous specification. Since configuration groups reside in
the SYS account, you do not specify the account name.
LOGON= accountname Default: LOGON=
OPERATOR.SYS
The logon account contains a standard logon. When the system is booted,
the account specified after LOGON= is used to initiate a session.
When SINGLE-USER has been specified, the account specified in
LOGON= is used as the single user. If LOGON= is not
specified on the command line, the logon defaults to OPERATOR.SYS
(if the OPERATOR.SYS user has been created).
RECOVERY or NORECOVERY
During a START or an autoboot after a DUMP, this option
indicates whether or not restartable jobs are restarted. On DUMP,
this option is in effect only if START is specified or defaulted.
If this option is not specified, the default is RECOVERY. Note on an
INSTALL or UPDATE, jobs cannot be restarted, and the next
START defaults to NORECOVERY.
Default: RECOVERY (except with START after
INSTALL or UPDATE)
Use NORECOVERY if the system configuration has changed. If
RECOVERY is specified and the system configuration has changed, the
system recovers restartable jobs by using the previous system configuration
and ignores the new system configuration and any GROUP=
specification.
SINGLE-DISC or MULTI-DISC (Primarily Used for
Diagnostics)
Default: MULTI-DISC
This option determines whether or not the system initiates with all of
the volumes mounted (MULTI-DISC) or only the system master volume
mounted (SINGLE-DISC). If neither is specified, MULTI-DISC
is the default. SINGLE-DISC can be specified only if
SINGLE-USER has also been selected. If the SINGLE-DISC
option is selected with MULTI-USER, the system issues a warning
message and changes the SINGLE-DISC option to MULTI-DISC.
If the START parameter is not specified or defaulted on an
INSTALL, UPDATE, or DUMP, the SINGLE-DISC
parameter is ignored.
SINGLE-USER or MULTI-USER (Primarily Used for
Diagnostics)
Default: MULTI-USER
This option boots the system with either single user capability or with
multiuser capability and all configured terminals available.
MULTI-USER is the default. SINGLE-USER is used primarily
for diagnostic support. For the INSTALL, UPDATE, and
DUMP utilities, the SINGLE-USER/MULTI-USER option is
available only if START is specified or defaulted as an
option.
START or NOSTART Default: START
This option instructs UPDATE, INSTALL, or DUMP
whether or not to autoboot (START) after the utility has completed
its job. If neither START nor NOSTART is specified,
START is the default.
SUBSET = ALL or SUBSET = MEMORY
Default:
SUBSET = ALL
During a dump, this option indicates whether the contents of main memory
alone or main memory and secondary storage is dumped to tape for later
analysis. If the subset is not specified, it defaults to ALL (main
memory and secondary storage).
SYSSTART or NOSYSSTART
Default:
SYSSTART
On an INSTALL, UPDATE, START, or
DUMP, this option determines whether or not the system startup file
is used during the current boot. If neither SYSSTART nor
NOSYSSTART is selected, SYSSTART (using the system startup
file) is the default. If the START parameter is not specified or
defaulted on an INSTALL, UPDATE, or DUMP, this
parameter is ignored.
Starts system from disk. If RECOVERY is used immediately after
changing system configuration, the system recovers restartable jobs by using
the previous system configuration and ignores the new system
configuration
Yes
Retained
START NORECOVERY
Starts system from disk. Use after changing system configuration. Use to
recover from system hang or failure.
Yes output only
Retained
UPDATE or UPDATE NOCONFIG
Boots system from the SLT. Replaces system files on disk with those from
SLT. System uses configuration files from disk. Use to update current version
of operating system while maintaining current configuration. Use to recover
from system hang or failure.
Yes output only
Retained
UPDATE CONFIG
Boots system from the SLT. Replaces system files with those on the SLT.
Replaces the configuration files on disk (in the group CONFIG.SYS)
with those from the SLT.
Yes output only
Retained
INSTALL or INSTALL START
Boots system from SLT. Replaces all system boot files and base system
files on the system volume (LDEV 1) with the information on the SLT. Replaces
configuration files with SLT defaults. Autoboots system after completing
install. Use to install a version of the operating system or to recover from
a disk crash or severe system failure.
No
Lost from system disks. User files remain on nonsystem
volumes.
INSTALLNOSTART
Performs similarly to INSTALL or INSTALL START, but
INSTALL NOSTART does not attempt to start the system after
completing the install.
No
Lost from system disks. User files remain on nonsystem
volumes.
DUMP
Boots system from disk. Stores current state of system main memory and
optionally secondary memory to tape for later analysis. Use to analyze causes
of system failure.