 |
» |
|
|
|
This section dicusses 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:
DUMP [SUBSET= { ALL [{ ;START
MEMORY }] ;NOSTART } [options]]
Where options are:
[{ ;RECOVERY [{ ;SINGLE-DISC
;NORECOVERY }] ;MULTI-DISC }]
[{ ;SINGLE-USER [{ ;SYSSTART
;MULTI-USER }] ;NOSYSSTART }]
|
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 is the same as specifying the following default options:
ISL> DUMP GROUP=CONFIG LOGON=OPERATOR.SYS MULTI-DISC &:
MULTI-USER RECOVERY START SUBSET=ALL SYSSTART
|
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. | | | | |
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 a Series 950 through
Series 980 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
CM> TC
Processor Dependent Code (PDC) revision 3.2
Console path = 2/4.1.0.0.0.0.0
Primary boot path = 2/4.0.0.0.0.0.0
Alternate boot path = 6/4.3.0.0.0.0.0
32 MB of memory configured and tested.
Autoboot from primary boot path enabled.
To override, press any key within 10 seconds.
**A key is pressed **
Boot from primary boot path (Y or N)?> Y
Interact with IPL (Y or N)?> Y
Booting.
Console IO Dependent Code (IODC) revision 4
Boot IO Dependent Code (IODC) revision 4
Booted.
MMSAVE Version 2.2
DUMPAREA found, save main memory to disc
ISL loaded
ISL Revision A.00.28 July 15, 1993
ISL> DUMP
MPE/XL launch facility
MPE/XL Dump Version A.00.00 - initialization
A full dump, including secondary storage, was requested.
Enter user identification string for this dump (80 chars or less):
TEST DUMP 6/9/88
Initialize_genesis - Version : <<870204.1552>>
WED, JUN 8, 1988, 2:30:04 PM (y/n)?
[TMUX_DAM] 15 7 12 14
Initialize memory manager completed.
MPE/XL Dump Facility Version A.00.00
Determine pre-compression size of secondary storage for ldev1
(52 Megabytes of transient objects will be dumped for this device.)
Determine pre-compression size of secondary storage for
ldev2
6 Megabytes of transient objects will
be dumped for this device Tape compression
enabled.
Density set at 6250 BPI on tape drive
tape is ready
Begin dump of Processor Internal Memory.
Processor Internal Memory dump complete.
Begin dump of main memory.
32 Megabytes of main memory will be dumped
.... .... .... ....
Dump of memory save area complete.
.... .... .... ....
Main memory dump complete.
Begin dump of secondary storage for ldev1
52 Megabytes of transient objects will be dumped for this device
.... .... .... .... .... .... .... .... .... .... .... .... ....
Secondary storage dump for ldev1 complete.
Begin dump of secondary storage for ldev2
7 Megabytes of transient objects will be dumped for this device
....
Secondary storage dump for ldev2 complete.
Dump completed - autoboot in progress.
Processor Dependent Code (PDC) revision 3.2
Console path = 2/4.1.0.0.0.0.0
Primary boot path = 2/4.0.0.0.0.0.0
Alternate boot path = 6/4.3.0.0.0.0.0
32 MB of memory configured and tested.
Soft Booted- -memory state is valid
Autoboot from primary path enabled.
To override, press any key within 10 seconds.
10 seconds expired- -proceeding with autoboot
Console IO Dependent Code (IODC) revision 4
Boot IO Dependent Code (IODC) revision 4
Booted.
MMSAVE Version 2.2
DUMPAREA protected, proceeding to ISL without memsave
ISL loaded
ISL Revision A.00.28 July 15, 1993
Cannot find an auto-execute file. AUTOBOOT ABORTED.
ISL>
|
Start the system. Enter the START command at the ISL
prompt and any desired options. Examples 3-5 and 3-6 and Appendix B “Startup, Dump, and Shutdown Listings” list the messages received at the console during a START.
ISL Summary | |
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.
START [;GROUP=cgn] [;LOGON=acct] [{ ;RECOVERY
;NORECOVERY }]
[{ ;SINGLE-DISC [{ ;SINGLE-USER
;MULTI-DISC }] ;MULTI-USER }]
[{ ;SYSSTART
;NOSYSSTART }]
|
When the START option of the UPDATE utility is selected, the remaining options are available.
UPDATE [{ ;CONFIG [{ ;START;
;NOCONFIG }] ;NOSTART } [options] ]
where options are: [;LOGON=acct][GROUP=cgn]
[{ ;SINGLE-DISC [{ ;SINGLE-USER
;MULTI-DISC }] ;MULTI-USER }]
[{ ;SYSSTART
;NOSYSSTART }]
|
When the START option of the INSTALL utility is selected, the remaining options are available.
INSTALL [{ ;START
;NOSTART } [options] ]
where options are: [;GROUP=cgn][LOGON=acct]
[{ ;SINGLE-DISC [{ ;SINGLE-USER
;MULTI-DISC }] ;MULTI-USER }]
[{ ;SYSSTART
;NOSYSSTART }]
|
When the START option of the DUMP utility is selected, the remaining options are available.
DUMP [ SUBSET= { ALL [{ ;START
MEMORY }] ;NOSTART }[options] ]
Where options are:
[{ ;RECOVERY [{ ;SINGLE-DISC
;NORECOVERY }] ;MULTI-DISC }]
[{ ;SINGLE-USER [{ ;SYSSTART
;MULTI-USER }] ;NOSYSSTART }]
|
All available options are defined in
Table 3-3 “Utility Options”. Table 3-3 Utility Options | Options | Functions |
|---|
CONFIG or NOCONFIG Default: NOCONFIG |
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 Default: RECOVERY (except with START after INSTALL or UPDATE) | 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. 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. |
Table 3-4 Utility Options | Options | Functions |
|---|
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. |
Table 3-5 “Summary of System Startup Functions” summarizes system startup utilities with their more commonly used options. Table 3-5 Summary of System Startup Functions | MPE/iX Utility | MPE/iX Function (When To Use) | Spool file Recovery | Permanent User Files |
|---|
| START or START RECOVERY | 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. | | INSTALL NOSTART | 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. | Yes output only | Retained |
|
