A fix is available
APAR status
Closed as program error.
Error description
After an abend in dump processing SDUMP can remain serialized resulting in message IEE711I SYSTEM DUMP NOT TAKEN. ANOTHER DUMP WAS IN PROGRESS for subsequent dump requests. In the reported problem case the logrec showed that dump processing abended S0C4 at IEAVTSSM+1968 while taking a dump for an address space in cross memory processing where the home, primary and secondary address spaces were all different and the dump request included all three address spaces. The problem generated the SDUMP request that abended S0C4 resulted in all three address spaces terminating end of memory. After the SDUMP end of memory resource manager processing, RTCTNAS had a negative value of FFFFFFFD resulting in SDUMP remaining serialized and preventing new dumps from being taken. In the reported problem case SDUMP processing abended S0C4 at IEAVTSSM+1968 before RTCTNAS was incremented to 00000003 to indicate that three address spaces were being dumped. The SDUMP end of memory resource manager, IEAVTSDR, was called for each address space termination and it decremented RTCTNAS without checking that the current value was > 0. This resulted in RTCTNAS being decremented from 00000000 to FFFFFFFF, and then to FFFFFFFE, and then to FFFFFFFD leaving SDUMP locked. Verification steps: Check RTCTNDAS via IPCS: IP SETD ACTIVE IP L 10?+23C?+1C LE(4) If this has a negative value, e.g. FFFFFFFF, then check logrec for an abend in SDUMP processing.
Local fix
Cancel DUMPSERV as it will restart automatically and clear RTCTNDAS.
Problem summary
**************************************************************** * USERS AFFECTED: All users of SVC dumps * **************************************************************** * PROBLEM DESCRIPTION: MSGIEA711I Another dump in progress * **************************************************************** * RECOMMENDATION: * **************************************************************** Dump processing was unavailable, and an operator initiated dump resulted in MSGIEE711I SYSTEM DUMP NOT TAKEN. ANOTHER DUMP WAS IN PROGRESS. LOGREC analysis showed that SDUMP processing experienced an ABEND 0C4 during summary dump processing. Further analysis revealed that SDUMP apparently failed to clean up correctly, for an address space that was going through end-of-memory termination.
Problem conclusion
SDUMP recovery for memory termination during TSDX summary dump processing was changed to set RtctNAS to the number of a/s in the RTCT table.
Temporary fix
Comments
APAR Information
APAR number
OA49395
Reported component name
SDUMP/ABDUMP
Reported component ID
5752SCDMP
Reported release
790
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-11-13
Closed date
2016-01-29
Last modified date
2016-03-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA80515 UA80514 UA80516
Modules/Macros
IEAVTSDR
Fix information
Fixed component name
SDUMP/ABDUMP
Fixed component ID
5752SCDMP
Applicable component levels
R7A0 PSY UA80514
UP16/02/10 P F602
R780 PSY UA80515
UP16/02/10 P F602
R790 PSY UA80516
UP16/02/10 P F602
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 March 2016