z/VM: CP Commands and Utilities Reference - z/VM - IBM

SET ABEND
Examples
Messages
3. There may be some unique circumstances which will prevent a dump from
being taken despite having the ABEND set to SNAPDUMP. This will only occur
if SNAPDUMP cannot get the resource which guarantees that no other
processor in the configuration will force the abending processor offline. If a
dump was to be taken at this time, its contents would not accurately reflect the
abending environment.
Invocations are cumulative, except for SET ABEND SOFT which resets all soft
abends to their system initialization settings. For example:
SET ABEND HARD ABC001 BCD002
Will add soft abends ABC001 and BCD002 to the abend table, indicating that they
should cause a hard abend if hit.
SET ABEND SNAP CDE003 DEF004 EFG005
The abend table will now have 2 soft abends set to hard (ABC001 and BCD002),
and 3 soft abends set to snapdump (CDE003, DEF004 and EFG005).
SET ABEND SOFT
HCP002E Invalid operand - operand
All soft abends are now in the original state they were in at system initialization
time. If any of the abends specified previously are hit, a normal soft abend dump
will be created.
HCP003E Invalid option - {option|command
contains extra option(s) starting with
option}
HCP026E Operand missing or invalid
HCP439E {User userid|*NSS|*IMG|*UCR|*NLS}
spool fileid limit exceeded
HCP475I Fatal I/O error trying to read directory
from volid [for user userid]
HCP1011E The hard/snapdump abend code table
is full.
HCP9309E CP was unable to allocate a soft abend
dump file.
HCP400I All {paging|spooling} space is in use.
HCP847E Maximum system spool file limit
exceeded
1192 z/VM: CP Commands and Utilities Reference
HCP9308I Spooling I/O error occurred while
reading or writing a system data file.