1 .TH ZGETDUMP 8 "Apr 2006" "s390-tools"
3 zgetdump \- tool for copying dumps.
5 \fBzgetdump\fR [-d] [-h] [-i] [-a] [-v] \fIdumpdevice\fR
7 \fBzgetdump\fR takes as input the dump device and writes its contents
8 to standard output, which you can redirect to a specific file.
10 \fBzgetdump\fR can also check, whether a DASD device contains a valid dumper.
14 Check DASD device \fIdumpdevice\fR for valid dumper.
20 Print the dump header information reading from the \fIdumpdevice\fR and
21 check if the dump is valid.
24 Print the dump header information and check if the dump is valid when
25 \fIdumpdevice\fR is a multi-volume tape.
26 (Mount and check all cartridges in sequence.)
29 Output version information and exit.
32 This parameter specifies the device or partition where the dump is located.
34 1. Scenario: DASD partition /dev/dasdx1 was prepared for dump by means of
38 The corresponding single-volume dump tool was IPLed.
39 .RB "The respective " "zgetdump " "call to copy the dump from the DASD
40 partition to file dump_file is:
43 zgetdump /dev/dasdx1 > dump_file
45 2. Scenario: DASD partitions /dev/dasdx1 and /dev/dasdy1 contained in file
46 dump_list_conf were prepared for dump by means of
48 zipl -M dump_list_conf
50 The corresponding multi-volume dump tool was IPLed.
51 .RB "The respective " "zgetdump " "call to copy the dump from the DASD
52 partitions to file dump_file is:
55 zgetdump /dev/dasdx > dump_file or equivalent
57 zgetdump /dev/dasdy > dump_file
59 3. Scenario: Tape device /dev/ntibm0 was prepared for dump by means of
63 The corresponding tape dump tool was IPLed.
64 .RB "The respective " "zgetdump " "call to copy the dump from the tape
68 zgetdump /dev/ntibm0 > dump_file