Explanation
A DUMPDS command requested that the system display
the status of SYS1.DUMP
nn data sets or automatic
allocation resources.
- The first part of the message displays the dump data sets that
were successfully processed.
- The second part of the message describes the dump data sets that
could not be processed and gives the reasons for each failure.
In the message text:
- NAME PATTERN [NOT] ACCEPTED:
- The system accepted or did not accept the name pattern you specified
on the NAME= command.
- pattern
- If the name pattern you specify on the NAME= command
is accepted, it is displayed.
- reason-text1
- If the name pattern you specify on the NAME= command
is not accepted, the system displays one of the following reasons:
- MISSING SYMBOLS: pattern
- You must specify the &SEQ. symbol as part of pattern.
- DSNAME TOO LONG: dsname
- dsname is a sample resolution of the data set
name pattern that you specified on the NAME= command.
Resolution of the name pattern resulted in a data set name longer
than 44 characters.
- INVALID DSNAME: dsname
- One or more of the qualifiers in dsname is
not specified correctly. Possible errors are:
- Leading numeric character
- More than 8 characters
- Incorrect characters.
- state
- In response to the ALLOC= command, the system
displays one of the following:
- ACTIVE
- The system will allocate dump data sets automatically.
- INACTIVE
- The system will not allocate dump data sets automatically.
- NOT ACTIVE
- If the system name begins with a numeric character, the ALLOC= command
will not allow automatic allocation if the &SYSNAME. symbol is
used incorrectly in the name pattern.
- reason-text2
- If you use &SYSNAME. incorrectly in the name pattern, the
system does not allow automatic allocation and displays the reason:
- SYSNAME BEGINS WITH NUMERIC. RESPECIFY NAME PATTERN. RETRY DUMPDS
- The &SYSNAME. symbol is defined with a leading numeric character.
You must change the name pattern or the system name.
- xx
- The suffix of the SYS1.DUMPnn name for a dump
data set.
- resource-type
- Specifies SMS CLASSES or DASD VOLUMES that you are adding or deleting
from the systems list of resources available for automatic allocation
of dump data sets.
- resources
- The names of the automatic allocation resources, either SMS classes
or DASD volumes.
- reason-text3
- If the system cannot complete an ADD, DELETE, or CLEAR request,
it displays one of the following reasons:
- ALREADY DEFINED TO SDUMP: xx,xx,xx-xx,
... or resource
- An attempt to add dump data sets or automatic allocation resources
failed because the data sets are already defined to receive SVC dumps.
- NOT DEFINED TO SDUMP: xx,xx,xx-xx,...
or resource
- An attempt to delete or clear dump data sets or automatic allocation
resources failed because the dump data sets are not defined to receive
SVC dumps.
- LOCATE FAILED: (xx,rc),(xx,rc),...
- An attempt to add dump data sets on a direct access storage device
(DASD) failed when the locate function returned a bad return code. rc is
the return code.
- NOT A DASD DATA SET: xx,xx,xx-xx,...
- An attempt to add DASD dump data sets failed because the device
type is not DASD.
- TRACKSIZE TOO SMALL: xx,xx,xx-xx,...
- An attempt to add DASD dump data sets failed because the track
size of the device is too small to hold a 4104-byte record.
- DYNAMIC ALLOCATION FAILED: (xx,rc,err,rsn),(xx,rc,err,rsn)
- A DYNALLOC macro to add DASD dump data sets failed because the
dynamic allocation failed. See z/OS MVS Programming: Authorized Assembler Services Guide for
a description of DYNALLOC return codes, error codes, and reason codes.
In the message text:
- xx
- The suffix of the SYS1.DUMPnn name for a data
set.
- rc
- The return code.
- err
- The error code for dynamic allocation.
- rsn
- The reason code for dynamic allocation.
- OPEN FAILED: xx,xx,xx-xx,...
- An attempt to add or clear DASD dump data sets failed because
the data sets failed to open.
- READ FAILED: xx,xx,xx-xx,...
- An attempt to add DASD dump data sets failed because the system
could not read the data set using BSAM READ.
- MULTIPLE VOLUME DATA SET NOT ALLOWED: xx,xx,xx-xx,...
- An attempt to add DASD dump data sets failed because they were
multivolume data sets, which are not allowed.
- EXCEEDS 100 DUMP DATA SET LIMIT: xx,xx,xx-xx,...
- An attempt to add dump data sets failed because the limit of 100
data sets has been reached.
- IN USE BY SDUMP: xx,xx,xx-xx,...
- An attempt to delete or clear dump data sets failed because SVC
dump was using the data sets.
- INVALID PRIMARY EXTENT SPACE: xx,xx,xx-xx,...
- An attempt to add DASD dump data sets failed because the data
set was allocated with zero primary extent space.
- UNEXPECTED ERROR: xx,xx,xx-xx,...
- An attempt to add, delete, or clear a dump data set caused a program
check or abnormal end. The system writes an SVC dump for this problem.
- { DASD VOLUMES | SMS CLASSES } NOT ADDED:
- AUTOMATIC ALLOCATION FAILED USING: resource, resource,
...
- Automatic allocation failed for a resource,
which is specified as a DASD volume serial number or an SMS storage
class in a DUMPDS ADD command. The volume or class cannot be used.
System action
The system continues processing.
Source
Module
Routing code
Descriptor code