DUMP (Dump Memory)

The DUMP (Dump Memory) command does the following tasks:

  • Performs a memory dump

  • Invokes the program dump procedure for specified programs

  • Sets up future program dump options

You can also perform a memory dump or a program dump with specified options.

Syntax

<memorydump option>

<programdump option list>

Explanation

DUMP

Interrupts processing on the system and initiates the memory dump process, which dumps the entire contents of memory or all in-use or partial memory. The type of memory dump depends on the memory dump option included with the dump request. If no option is specified, a COMPLETE memory dump will be taken. The setting of the MDT option does not affect the type of memory dump for operator requests.

For additional information, refer to the MDT (Memory Dump Type) command. For information about how to handle the memory dump process, refer to “Memory Dump Processing,” “??DUMP (Dump Memory),” and “??MEMDP (Dump Memory).”

DUMP <text>

Causes the first 18 characters of <text> to appear in the memory dump as the reason for the dump.

DUMP : <memorydump options>

Specifies an option for a memory dump. The following table describes the valid values.

Memory Dump Option

Description

PARTIAL

Captures a subset of the in-use areas of memory. A partial dump includes the following areas:

  • The requested stack and all the areas owned by the stack.

  • The area occupied by all the stacks in a running system.

  • All the areas owned by the MCP.

  • Any stack and its associated areas that are linked into the GRAPHHEADWORD, PROCESSFAMILYLINK, or both of the requested stack.

  • ASD tables.

If you do not supply a mix number with this option , the MCP performs a dump of the CONTROLLER stack.

MINIMAL

Captures a subset of the information contained in the dump. A minimal dump includes the following:

  • The ASD table.

  • The area occupied by all the stacks in a running system the area from the bottom-of-the-stack register (BOSR) to the limit-of-stack register (LOSR) of each stack.

  • The structures owned by the MCP required for the DUMPANALYZER SUMMARY and STACK commands, including all PIBS, TABW, and JOBDATA information.

  • The LISTARRAY containing GRAPH information.

  • For DIAGNOSTIC MCPs, the TRACE BUFFER, TBIT_RCWS, and ASD_LOCK_WORD arrays.

  • When a mix number is supplied, the off stack information of the process family of the mix number is also included in the dump.

ALLINUSE

Captures only the in-use areas (those present in memory).

COMPLETE

Captures the entire memory image.

PDUMP

Initiates the MCP independent runner MCPPDUMPHANDLER to request a program dump to disk containing system information normally not included in a user-requested program dump. Specific MCP code determines the additional system information that is included in the program dump.

While DUMP <text> is allowed in the command syntax, it only appears in the system log as a comment and as parameters in the MCPPDUMPHANDLER stack.

Note: The PDUMP option is not intended for customer use and should only be used when instructed to do so by Unisys personnel.

<mix number list> DUMP

Invokes the program dump procedure for the programs in the mix number list.

<mix number list> DUMP <programdump option list>

Specifies options to control a program dump. These options are as follows.

Option

Description

* (asterisk)

Combines options already set by the task with options specified in the command; the net result controls the program dump.

ALL

Sets all future dump options, including DSED and FAULT. No program dump is taken at this time (when the command is entered).

ARRAYS

Dumps the arrays.

BASE

Dumps the base of the stack (used by the operating system) and the process information block.

CODE

Dumps all code segments.

CRITICALBLOCK

Causes any program dumps to include the stack that contains the critical block of the dumping stack. If the stack is a job stack, it is not dumped. The stack is dumped from the top of the environment that contains the critical block or from the base of the frozen environment of a library or database stack, whichever is higher.

DBS

Dumps database stacks.

DSED

Requests a future program dump if the program is discontinued (with a DS command) for any reason other than a fault. No program dump is taken at this time (when the command is entered).

FAULT

Requests a future program dump if a fault (such as a segmented array or a divide-by-zero operation) occurs in the program. No program dump is taken at this time (when the command is entered).

FILES

Dumps all areas used by files.

LIBRARIES

Dumps library stacks.

NONE

Resets all future program dump options. If no other options are specified in this command, a dump is taken with the default options.

PRESENTARRAYS

Dumps only present arrays. If the ARRAYS option and the PRESENTARRAYS option are both specified, then all arrays are dumped.

PRIVATELIBRARIES

Dumps only private library stacks. If LIBRARIES is also set, the system dumps all libraries.

TODISK

Causes any program dumps taken by the process to be directed to a disk file. If TOPRINTER is also set, the system directs the dump both to the printer and to disk.

TOPRINTER

Causes any program dumps taken by the process to be directed to the task file. The INTNAME of this file is TASKFILE, and the default KIND is PRINTER. If TODISK is also set, the system directs the dump both to disk and to the printer.

For details about the effects of the TODISK and TOPRINTER options, refer to the Task Attributes Programming Reference Manual.

When the DUMP command is invoked for a program, the dump options for that program are permanently set or reset. If the asterisk (*) option is not specified, all the dump options are reset, except those explicitly specified in the command.

On a system with the Secure Access Control Module security enhancements or with the Security Accountability Facility, when the PROGDUMPFILTER option is set, a dump taken TOPRINTER contains only the data belonging to the environment of the dumping program. The data in a dump taken TODISK is filtered to display only the data belonging to the environment of the dumping program, unless the dump is analyzed by a privileged user or process.

Examples

Example 1

This example shows a program dump that sets all options for the program with the specified mix number: 

3132 DUMP ALL

Example 2

This example requests a partial memory dump for the program with the specified mix number: 

DUMP : PARTIAL 5402

Example 3

These two examples request minimal memory dumps by using the DUMP command with the MINIMAL <memorydump option>: 

DUMP LOW_MEMORY:MINIMAL
DUMP TASK_LOOPING:MINIMAL 1024

Example 4

These two examples use the PDUMP option to request that MCP diagnostic information be captured without interrupting the system for a memory dump: 

DUMP :PDUMP
DUMP MCP PROGDUMP: PDUMP

Considerations for Use

When the system is performing a memory dump, the MCP clock stops. As a result, the processor and I/O times for various actions are not distorted by the time used to take the dump.

Prev  Up  Next
DU (Disk Utilization)  Home  ENCRYPT