HP 3000 Manuals HP 3000 Manuals
Managing the Dump-to-Disk and Mini-Dump Features
[REV END]
Use the AutoRestart/iX BLDDUMP utility to manage dump files. The BLDDUMP
utility provides a set of easy-to-use commands that allow you to perform
the tasks required to manage the[REV BEG] dump-to-disk and mini-dump
features.[REV END] Following is a summary of BLDDUMP commands and their
functions:
Table 3-1. Summary of BLDDUMP Commands
--------------------------------------------------------------------------------------------
| | |
| Command Name | Function |
| | |
--------------------------------------------------------------------------------------------
| | |
| ALTSIZE | Alters the size of a specified dump file. |
| | |
--------------------------------------------------------------------------------------------
| | |
| AUTOBOOT | Allows you to enable or disable the autoboot feature for system startup. |
| | |
--------------------------------------------------------------------------------------------
| | |
| BUILD | Builds a dump file with the specified name, size in megabytes, and |
| | protection scheme (protected or unprotected).[REV BEG] |
| | |
--------------------------------------------------------------------------------------------
| | |
| BUILDMD | Builds the mini-dump file with the specified size in number of 80-byte |
| | records.[REV END] |
| | |
--------------------------------------------------------------------------------------------
| | |
| CMDL | Displays a list of available BLDDUMP commands. |
| | |
--------------------------------------------------------------------------------------------
| | |
| DO | Allows you to immediately reinvoke a previously invoked BLDDUMP command |
| | (same as the CI DO command). |
| | |
--------------------------------------------------------------------------------------------
| | |
| EXIT | Exits BLDDUMP. |
| | |
--------------------------------------------------------------------------------------------
| | |
| HELP | Displays information about BLDDUMP command syntax, parameters, and |
| | usage.[REV BEG] |
| | |
--------------------------------------------------------------------------------------------
| | |
| INITMD | Initializes the file that contains the information defining the contents |
| | of the mini-dump. The default file, MDINPUT.HP36375.TELESUP, defines the |
| | contents of the mini-dump. |
| | |
| | Initializes the file containing the criteria for specified system |
| | failures.[REV END] |
| | |
--------------------------------------------------------------------------------------------
| | |
| LIST | Lists the current status of dump files, including maximum configured |
| | size, protection scheme, and the size of current contents. The LIST |
| | command also specifies whether or not the DUMP facility dumps to tape if |
| | dump-to-disk is unsuccessful.[REV BEG] |
| | |
--------------------------------------------------------------------------------------------
| | |
| LISTMD | Lists information pertaining to the mini-dump.[REV END] |
| | |
--------------------------------------------------------------------------------------------
| | |
| LISTREDO | Displays all commands invoked during the current session of BLDDUMP (same |
| | as the VI REDO command). |
| | |
--------------------------------------------------------------------------------------------
| | |
| PROTECT | Alters the protection scheme of a dump file. |
| | |
--------------------------------------------------------------------------------------------
| | |
| PURGE | Purges the specified dump file.[REV BEG] |
| | |
--------------------------------------------------------------------------------------------
| | |
| PURGEMD | Purges the specified mini-dump file.[REV END] |
| | |
--------------------------------------------------------------------------------------------
| | |
| RESET | Resets a dump file to indicate zero contents, thus readying it for a |
| | subsequent dump. |
| | |
--------------------------------------------------------------------------------------------
| | |
| REDO | Allows you to respecify any previously invoked BLDDUMP command for |
| | modification prior to reinvoking it (same as the CI REDO command). |
| | |
--------------------------------------------------------------------------------------------
| | |
| RESET | Resets a dump file to indicate zero contents, thus readying it for a |
| | subsequent dump. |
| | |
--------------------------------------------------------------------------------------------
| | |
| TAPE | Specifies your alternate dump device strategy. Indicates whether or not |
| | the DUMP facility dumps to tape if it cannot store complete dump |
| | information to disk. |
| | |
--------------------------------------------------------------------------------------------
The BLDDUMP prompt provides a number in parentheses that indicates the
number of BLDDUMP commands invoked during the current session of BLDDUMP
(helpful for use with the DO and REDO commands). For example, (#4)
blddump > indicates that three previous BLDDUMP commands have been
invoked in the current session of BLDDUMP.
Specify the alternate dump device strategy
Use the TAPE command to specify whether or not the dump facility
initiates a dump-to-tape if it cannot write complete dump information to
a dump file on disk. The default is YES. If NO is specified, the dump
facility writes to EOF and terminates if it cannot write complete dump
information to disk.
TAPE command syntax.
TAPE dump_strategy
TAPE command parameters.
dump_strategy Optional. If Y[es] is specified, the dump facility
initiates dump-to-tape if dump-to-disk is unsuccessful. If
N[o] is specified, the dump facility terminates immediately
if dump-to-disk is unsuccessful. If neither is specified,
TAPE defaults to YES.
For more information about specifying your dump strategy, refer to
"Defining Your Alternate Dump Device Strategy," earlier in this chapter.
TAPE command example.
To indicate that you want to terminate the dump if dump-to-disk is
unsuccessful, enter the following at the BLDDUMP prompt:
(#1) blddump > TAPE NO
Building a dump file
Use the BUILD command to build a dump file. You can build up to 10 dump
files. The BUILD command enables you to specify the following about the
dump file:
* the dump file ID
* the maximum number of megabytes that can be written to the file
* the protection scheme
BUILD command syntax.
BUILD fileid, file size [,protection]
NOTE Building dump files on the MPEXL_SYSTEM_VOLUME_SET can cause
problems. To ensure a successful creation of a new dump file on
the MPEXL_SYSTEM_VOLUME_SET, a CTRL A shutdown must be performed.
For example:
(#2) blddump > BUILD TEST 100 N
(#2) blddump > E
:CTRL A
=SHUTDOWN
CTRL B
CM> CTRL M
ISL> START NORECOVERY
If a dump is required before the dump file label is posted to disk,
then DISKDUMP fails.
BUILD command parameters.
fileid Required. The fileid parameter specifies the name
of the dump file that you want to create. The
fileid parameter can be up to five alphanumeric
characters in length and must begin with an alpha
character. The BLDDUMP utility appends the
characters MEM to fileid. For example, DUMP1
becomes DUMP1MEM.
file size Required. The size, in megabytes, of the dump
file. The size of the dump file should be greater
than the largest dump possible on the system. (The
DTODSIZ utility provides you with this
information.)
protection Optional. If Y[es] is specified, the dump file is
protected from overwrites by subsequent dumps to
disk, if it contains dump data. If N[o] is
specified, subsequent dumps to disk can write new
dump data to the file, deleting any existing data.
YES is the default.
BUILD command example.
To build a protected dump file named DUMP1 with a size of 417 megabytes
and its contents protected from overwrites, enter the following at the
BLDDUMP prompt:
(#2> blddump > BUILD DUMP1 417 Y
Building new Dumpfile.
This can take a while...
NOTE The process of building a large dump file takes time. Large dump
files can take 15 minutes or more to create.
If you invoke BUILD, you must invoke both VSCLOSE and VSOPEN against the
nonsystem volume set when you exit BLDDUMP. This ensures posting of
directory information. At the system prompt, enter:
:VSCLOSE DISKDUMP_VOLUME_SET
:VSOPEN DISKDUMP_VOLUME_SET
[REV BEG]
Building a mini-dump file
Use the BUILDMD command to build a mini-dump file. One mini-dump file
only is allowed. In order to protect it from being overwritten by a
subsequent mini-dump, you must copy it to another file prior to invoking
the INITMD command.
The BUILDMD command enables you to specify the maximum number of records
that can be written to the file.
BUILDMD command syntax.
BUILDMD filesize
BUILDMD command parameters.
filesize Required. The size, in 80-byte records, of the
mini-dump file.
BUILDMD command example.
To build a mini-dump file of 500 80-byte records, enter the following at
the BLDDUMP prompt:
(#2> blddump > BUILDMD 500
This builds a mini-dump file named MINIDUMP in the group and account
MPEXL.SYS.[REV END]
[REV BEG]
Initializing a mini-dump file
The INITMD command initializes two files; the mdinput file that defines
the contents of the mini-dump, and the mdinfo file that contains the
criteria action to be taken for specified system failures.
INITMD command syntax.
INITMD mdinput mdinfo
INITMD command parameters.
NOTE If no parameters are specified, all files currently initialized
become uninitialized, and the mini-dump feature is disabled.
mdinput Optional. The file containing the SAT commands
that define the contents of the mini-dump. This
file must be an unnumbered, 80-byte record file.
The mini-dump consists of the output from a SAT
session based on a set of supplied commands.
When the option SATINIT is specified, SAT
automatically executes the file commands that were
initialized through the INITMD command. The
MDINPUT.HP36375.TELESUP template contains the
minimum set of SAT commands that must be used to
create the mini-dump with a date and time stamp,
the MPE/iX version number, system failure
information, and a stack trace. If these commands
are not specified in your file, the mini-dump may
not be created or its contents could be
incorrect.[REV END]
[REV BEG]
mdinfo Optional. The file containing the action criteria.
This file must be an unnumbered, 80-byte record
file.
The mdinfo file that you create must specify the
action to take based on the system failure number
specified. The two actions that can be taken are
to perform a full dump (FULLDUMP) or to not perform
a full dump (NULLDUMP). To specify that a mini-dump
should be taken for all system failures, then the
ASCII string DEFAULT must be placed on the first
line of the file followed by the action NULLDUMP
(do not perform a full dump).
For example, to create an mdinfo file that will
perform a mini-dump for all system failures except
a system abort number 1451 and a sudden death
number 311, you would create the following
unnumbered temporary (TEMP) file:
_____________________________________
| |
| DEFAULT NULLDUMP |
| SA1451 FULLDUMP |
| SD311 FULLDUMP |
| EOF |
_____________________________________
[REV END][REV BEG]
When you have completed the contents of your
temporary file (TEMP), keep the contents as an
unnumbered file, build a permanent mdinfo file, and
copy the contents of the TEMP file to it. At the
system prompt, enter:
:BUILD mdinfo;REC=-80,,F,ASCII
:FCOPY FROM=TEMP;TO=mdinfo
:PURGE TEMP
[REV END][REV BEG]
INITMD command example.
To initialize a mini-dump file with MDINPUT containing the SAT commands
and MDINFO containing the action criteria, enter the following at the
BLDDUMP prompt:
(#1> blddump > INITMD MDINPUT MDINFO
The INITMD command reinitializes the mini-dump file to blank records;
therefore, you must copy it to another name before using the INITMD
command. Once the INITMD command is invoked, you cannot access the
mini-dump file, and any attempts to view or text the file fails.
The INITMD command must be used each time the file containing the action
criteria is modified, or after you purge the mini-dump file and build a
new one, and each time the system is reset.
To ensure that the INITMD command is used each time the system is reset,
the following can be placed in a job and streamed in the SYSSTART file:
:JOB MINI,MANAGER.SYS,PUB;OUTCLASS=LP,2
:COPY MINIDUMP.MPEXL.SYS,MINISAVE
:RUN BLDDUMP.HP36375.TELESUP;INFO="INITMD mdinput,mdifo;EXIT"
:EOJ
The last execution of INITMD determines which files are initialized.[REV
END]
Purging a dump file
Use the PURGE command to purge a dump file from the nonsystem volume set.
Dump files are specially protected files and can be purged only through
the BLDDUMP utility. The PURGE command available through the command
interpreter does not remove a dump file from your system.
NOTE Do not purge a dump file until you have determined that you no
longer need its contents and that you no longer need the space
allocated.
PURGE command syntax.
PURGE fileid
PURGE command parameters.
fileid Required. The fileid parameter is the name of the existing
dump file that you want to purge. Do not specify the
characters MEM, appended by BLDDUMP.
PURGE command example.
To purge a file named DUMP1, enter the following at the BLDDUMP prompt:
(#3) blddump > PURGE DUMP1
The BLDDUMP utility asks you to reaffirm your intention to purge the
file. Respond Y to purge the file.
If you invoke PURGE, you must invoke both VSCLOSE and VSOPEN against the
nonsystem volume set when you exit BLDDUMP. This ensures posting of
directory information. You must enter VSCLOSE and VSOPEN at the console.
At the system prompt, enter:
:VSCLOSE DISKDUMP_VOLUME_SET
:VSOPEN DISKDUMP_VOLUME_SET
NOTE Do not purge a dump file when it is being accessed by another
process (for example, during dump analysis or during a
store-to-tape). If you try to purge a dump file being accessed,
BLDDUMP asks you if you want to purge the file from BLDDUMP. Do not
purge the dump file. Instead, wait to purge it until after access
is complete.
[REV BEG]
Purging a mini-dump file
Use the PURGEMD command to purge a mini-dump file. Mini-dump files are
specially protected files and can be purged only through the BLDDUMP
utility. When you use the PURGEMD command to purge your mini-dump file,
it invalidates the system data structures that contain information
regarding the mini-dump; therefore, if you use the BUILDMD command to
build another mini-dump file, the INITMD command must be invoked to
reinitialize the files that contain the SAT commands and dump criteria.
NOTE Do not purge a mini-dump file until you have determined that you no
longer need its contents and that you no longer need the space
allocated.
PURGEMD command syntax.
PURGEMD
PURGEMD command example.
To purge the mini-dump file, enter the following at the BLDDUMP prompt:
(#3) blddump > PURGEMD
The BLDDUMP utility asks you to reaffirm your intention to purge the
mini-dump file. Respond Y to purge the file.[REV END]
Reseting a dump file
Use the RESET command to delete or reset the contents of a dump file
without altering the file's size or protection scheme. Invoking RESET on
a dump file empties it. After you reset a dump file, a subsequent
dump-to-disk can write to the empty dump file. You should reset a dump
file after you analyze the dump information.
NOTE Even after a dump file has been reset, it still contains readable
dump information; however, the dump-to-disk feature can now write
new dump information to it, even if it is a protected dump file.
RESET command syntax.
RESET fileid
RESET command parameters.
fileid Required. The fileid parameter is the name of the existing
dump file with contents that you want to delete. The file
size (configured by BUILD or ALTSIZE) and the protection
scheme (configured by BUILD or PROTECT) are not altered.
Do not specify the characters MEM, appended by BLDDUMP.
RESET command example.
To empty the contents of the dump file DUMP1, enter the following at the
BLDDUMP prompt:
(#4 blddump > RESET DUMP1
Altering the size of a dump file
Use the ALTSIZE command to alter the size of a dump file. Use this
command when the dump file is too large (wasting disk space) or too small
(causing unsuccessful dumps to disk). ALTSIZE purges the dump file, then
creates a new dump file of the same name and protection scheme. Any
contents in the dump file are lost.
NOTE Do not alter the size of a dump file until you have determined that
you no longer need its contents.
Because ALTSIZE can take some time, BLDDUMP asks you to reaffirm your
intention to alter the size of a file. Respond Y to alter the file size.
After you have initially configured dump files, use the DTODSIZ utility
periodically during your system's peak operating periods to predict more
closely the required dump file size.
ALTSIZE command syntax.
ALTSIZE fileid, newsize
ALTSIZE command parameters.
fileid Required. The fileid parameter is the name of the existing
dump file that you want to enlarge or reduce. Do not
specify the characters MEM, appended by BLDDUMP.
newsize Required. The new size, in megabytes, of the dump file.
The size of the dump file should be greater than the
largest dump possible on the system. The DTODSIZ utility
provides you with this information.
ALTSIZE command example.
To alter the maximum configurable size of a dump file DUMP1 to 417
megabytes, enter the following at the BLDDUMP prompt:
(#5 blddump > ALTSIZE DUMP1 417
If you invoke ALTSIZE, you must invoke both VSCLOSE and VSOPEN against
the nonsystem volume set when you exit BLDDUMP. This ensures posting of
directory information. You must enter VSCLOSE and VSOPEN at the console.
At the system prompt, enter:
:VSCLOSE DISKDUMP_VOLUME_SET
:VSOPEN DISKDUMP_VOLUME_SET
NOTE Do not alter the size of a dump file when it being accessed by
another process (for example, during dump analysis or during a
store-to-tape). If you try to alter the size of a dump file being
accessed, BLDDUMP asks you if you want to purge the file from
BLDDUMP. Do not purge the dump file. Instead, wait to purge it
after access is complete.
Changing a dump file's protection scheme
Use PROTECT to alter the protection scheme of a dump file. You can
either protect a dump file from overwrites by subsequent dumps to disk,
or leave it unprotected.
PROTECT command syntax.
PROTECT fileid [,protection_scheme]
PROTECT command parameters.
fileid Required. The fileid parameter is the name of an existing
dump file with a protection scheme that you want to alter.
Do not specify the characters MEM, appended by BLDDUMP.
protection Optional. If Y[es] is specified, the dump file containing
_scheme
dump data is protected from overwrites by subsequent dumps
to disk. If N[o ] is specified, subsequent dumps to disk
can write new data to the file. YES is the default.
PROTECT command example.
To remove protection from DUMP2, enter the following at the BLDDUMP
prompt:
(#6) blddump > PROTECT DUMP2 NO
Listing dump-to-disk information
Use the LIST command to review the following information:
* Current status of all dump files, including file size, size of
contents, and protection scheme.
* Alternate dump device strategy. Determine if the dump facility
initiates dump-to-tape if it cannot write complete dump
information to a disk dump file.
* Current status of the autoboot feature. Determine if the autoboot
feature is enabled or disabled.
LIST command syntax.
LIST
LIST command example.
To list the current status of the dump-to-disk feature, enter the
following at the BLDDUMP prompt:
_______________________________________________________________________
| |
| |
| (#7) blddump > LIST |
| |
| Autoboot Status OFF |
| Dump-to-tape if dump-to-disk is not successful? NO |
| |
| DUMP FILE NAME DUMP FILE CURRENT SIZE PROTECTED? |
| (ID + "MEM") MAXIMUM SIZE OF CONTENTS |
| (megabytes) (megabytes) |
| -------------- ------------ ------------- ---------- |
| DUMP1MEM 417 0 YES |
| |
_______________________________________________________________________
[REV BEG]
Listing mini-dump information
Use the LISTMD command to review the following information:
* current mini-dump version
* current status of the autoboot, restart, and mini-dump features
* current mini-dump record size, input file and when it was
initialized, and the criteria file and when it was initialized
[REV END][REV BEG]
LISTMD command syntax.
LISTMD
[REV END][REV BEG]
LISTMD command example.
To list the current status of the mini-dump feature, enter the following
at the BLDDUMP prompt:
_____________________________________________________________________
| |
| |
| (#1) blddump > LISTMD |
| |
| Mini-Dump Version A.00.00 |
| |
| Autoboot Status ON |
| Restart Enabled YES |
| Mini-Dump Enabled YES |
| |
| MINI-DUMP FILE:MINIDUMP.MPEXL.SYS |
| MAXIMUM RECORDS: 500 |
| |
| INPUT FILE: MDINPUT.MYGROUP.SYS |
| INITIALIZED: FRI, JUL 3, 1992, 1:10 PM |
| |
| DUMP CRITERIA FILE: MDINFO.MYGROUP.SYS |
| INITIALIZED: FRI, JUL 3, 1992, 1:35 PM |
| |
_____________________________________________________________________
[REV END]
Displaying the autoboot status
Use the AUTOBOOT command to display the current status of autoboot and
toggle the autoboot flag.
AUTOBOOT command syntax.
{ON }
AUTOBOOT {OFF }
{STATUS}
AUTOBOOT command parameters.
ON Optional. The ON option enables the autoboot feature.
OFF Optional. The OFF option disables the autoboot feature.
STATUS Optional. The STATUS option displays the current status of
the autoboot feature. For example, a message similar to
the following is displayed:
Autoboot is enabled.
AUTOBOOT command example.
To enable the autoboot feature, enter the following at the BLDDUMP
prompt:
(#1) blddump > AUTOBOOT ON
A message similar to the following is displayed:
Autoboot is already enabled.
NOTE This message indicates that the autoboot feature was already set to
ON.
Using the BLDDUMP help facility
Use the HELP command to review detailed information about BLDDUMP
commands. If you enter HELP alone, you see a syntax description of all
BLDDUMP commands. If you enter HELP with a command name, you see
detailed information about that command.
HELP command syntax.
HELP [cmd_name] [options]
HELP command parameters.
cmd_name Optional. The name of a BLDDUMP command. The value for
cmd_name can be any of the following: TAPE, BUILD, PURGE,
ALTSIZE, AUTOBOOT, PROTECT, RESET, LIST, HELP, or EXIT.
options Any combination of the following: [NO]USE, NO[PARMS],
NO[DESC], NO[EXAMPLE], NO[ACCESS], ALL
HELP command example.
To list the detailed information about the ALTSIZE command, enter the
following at the BLDDUMP prompt:
(#8) blddump > HELP ALTSIZE,USE
Exiting the BLDDUMP utility
Use the EXIT command to exit the BLDDUMP utility.
If you invoke BUILD, PURGE, or ALTSIZE, you must invoke both VSCLOSE and
VSOPEN against a nonsystem volume set when you exit BLDDUMP. This ensures
posting of directory information. You must enter VSCLOSE and VSOPEN at
the console specifying the nonsystem volume set name. For example, if
you invoked the BUILD command against a nonsystem volume set named
DISKDUMP_VOLUME_SET then, at the system prompt, enter:
:VSCLOSE DISKDUMP_VOLUME_SET
:VSOPEN DISKDUMP_VOLUME_SET
EXIT command syntax.
EXIT
EXIT command example.
To exit BLDDUMP, enter the following at the BLDDUMP prompt:
(#9) blddump> EXIT
If a nonsystem volume set (for example, EXAMPLE_SYSTEM_VOLUME_SET) is
selected, then the following is displayed:
Remember to do a VSCLOSE and then a VSOPEN
on EXAMPLE_SYSTEM_VOLUME_SET.
If the system volume set MPEXL_SYSTEM_VOLUME_SET is selected, then
nothing is displayed. This is because you cannot perform a VSCLOSE or a
VSOPEN on the system volume set.
NOTE Hewlett-Packard does not recommend that you use the system volume
set for dump-to-disk. If the system comes down before it can post
information to the MPEXL_SYSTEM_VOLUME_SET disk directory, then you
cannot perform the dump-to-disk on this failure. Since the disk
directory format is posted at startup time, subsequent
dumps-to-disk will be successful.