Explanation
Depending on the message text, the message means:
- INSTALLATION PREDUMP EXIT, dumpexit, MODIFIED/SUPPRESSED
THE DUMP REQUEST
- The dump was suppressed by the installation predump exit. In the
message text:
- dumpexit
- The most recent exit that requested suppression.
- NO DUMP WAS PRODUCED FOR THIS ABEND, DUE TO SYSTEM OR INSTALLATION
REQUEST
- The system or installation requested no dump for this abend.
- DUMP SUPPRESSED - USER NOT AUTHORIZED BY SAF
- The system authorization facility (SAF), resource access control
facility (RACF®), or its equivalent,
determined that the caller does not have authority to dump the program
that was running at the time of the error.
- DUMP SUPPRESSED - ABDUMP SERIALIZATION DEADLOCK AVOIDED, SVC DUMP
TAKEN INSTEAD
- ABDUMP (SYSUDUMP, SYSMDUMP, or SYSABEND) processing
could not produce a dump because another task held a critical resource.
The resource was held for an interval that was longer than the value
set for the TIMEENQ option of ABDUMP. An SVC dump was taken instead,
capturing system data for later analysis. The dump title includes
the JOBNAME of the abending task. Processing continues, since the
potential deadlock was avoided.
- DUMP SUPPRESSED - ABDUMP SERIALIZATION DEADLOCK AVOIDED, SVC DUMP
FAILED RC=sscc
- ABDUMP (SYSUDUMP, SYSMDUMP, or SYSABEND) processing
could not produce a dump because another task held a critical resource.
The resource was held for an interval that was longer than the value
set for the TIMEENQ option of ABDUMP. Processing continues, since
the potential deadlock was avoided. An attempt was made to take
an SVC dump, but the system was unable to take the dump. The return
code indicates this with a value of X'08'. The reason codes
describe the specific cause. Some applications reason codes are:
- 02
- The capture phase of another SVC dump was in progress.
- 04
- The SVC dump was suppressed by a SLIP NODUMP command.
- 0B
- The dump was suppressed by DAE.
Refer to z/OS MVS Programming: Authorized Assembler Services Reference LLA-SDU for
a complete description of the SDUMPX macro return reason codes.
In
the message text:
- ss
- The SDUMPX reason code.
- cc
- The SDUMPX return code.
- DUMP SUPPRESSED - ABDUMP MAY NOT DUMP STORAGE FOR KEY 0-7 JOB jobname
- ABDUMP did not produce a dump because the storage access key for
the task is authorized, between 0 and 7. The program that issued
the ABEND may still dump data via one of the following methods:
- Use the SDUMP macro to obtain a dump, or
- Use the SNAP macro to selectively dump data areas.
Alternately, a SLIP trap can be set to request
that an SVC dump be generated for the ABEND. Also, the installation
may allow the user to receive these dumps by permitting the user to
have READ access to the IEAABD.DMPAKEY FACILITY as described in the z/OS Security Server RACF Security Administrator's Guide.
System action
The system suppresses the ABDUMP.
In the case of DEADLOCK AVOIDED, an SVC dump can be generated, associated
with ABEND X'333', reason codeX' 30'. LOGREC data
contains the name of the resource and the JOBNAME that the dump was
taken for.
System programmer response
- For INSTALLATION PREDUMP EXIT or NO DUMP WAS PRODUCED make sure
that the system does not suppress needed dumps.
- For USER NOT AUTHORIZED, the security authority can be changed
to allow the application programmer to get the necessary dump by permitting the user to have READ or UPDATE access
to the IEAABD.DMPAUTH facility as described in the z/OS Security Server RACF Security Administrator's Guide.
- For ABDUMP MAY NOT DUMP, the security authority can be changed
to allow the application programmer get the necessary dump. Note that
the dump can contain sensitive installation data since fetch protected
storage is included in this dump.
- For DEADLOCK AVOIDED several options are available:
- When an SVC dump is available, analysis of the potential hang
condition can be done using the IPCS VERBEXIT GRSTRACE or ANALYZE
RESOURCE command against the dump. Search for the MAJOR names SYSZTIOT
and SYSIEA01. The resource, which ABDUMP detected the possible deadlock
condition for, will have multiple tasks (TCBs) listed for the same
MINOR name. One of the following conditions may exist:
- The TCB holding the resource exclusively may have a programming
error.
- Multiple ABDUMPs could be processing and the first one is holding
the SYSIEA01 enqueue longer than the TIMEENQ interval allowed.
- The detection interval can be changed if either SVC dumps are
being generated too often for the installation, or if hangs are not
being detected quickly enough. The interval can be changed using the
CHNGDUMP SET,ABDUMP,TIMEENQ = nnnn command. Once a value is determined
for the installation, the command should be placed into a COMMNDxx
member of PARMLIB. This ensures the setting as the installation default
when the system is IPLed.
- All associated dumps can be suppressed by using the following
command:
SLIP SET,C=333,ID=X333,A=NOSVCD,REASON=30,END
Programmer response
If a dump needed to diagnose a problem was
suppressed, notify the system programmer.
Source
Module
Routing code
Descriptor code