Question & Answer
Question
System dump captured with SOME STORAGE COULD NOT BE DUMPED RC=8 TASKS RESET DISPATCHABLE PRIOR TO DUMP COMPLETION Attaching full system log info: IEA794I SVC DUMP HAS CAPTURED: 327 DUMPID=002 REQUESTED BY JOB (PBP2DIST) DUMP TITLE=PBP2,ABND=04E-00E60189,U=PBPDRDA ,M=N ,C=101.LOCN=: :146.215.131.79 ,LOC=DSNWVAPR.DSNWVAPR+2A08 IGD17287I DATA SET SYS1.SAPPRD2.DMP00002 328 COULD NOT BE ALLOCATED NORMALLY, SPACE CONSTRAINT RELIEF (MULTIPLE VOLUMES) WILL BE ATTEMPTED IGD17286I SPACE CONSTRAINT RELIEF WAS USED TO ALLOCATE DATA SET 329 SYS1.SAPPRD2.DMP00002, DATA WAS SPREAD OVER MULTIPLE VOLUMES IEF196I IGD17287I DATA SET SYS1.SAPPRD2.DMP00002 IEF196I COULD NOT BE ALLOCATED NORMALLY, IEF196I SPACE CONSTRAINT RELIEF (MULTIPLE VOLUMES) WILL BE ATTEMPTED IEF196I IGD17286I SPACE CONSTRAINT RELIEF WAS USED TO ALLOCATE DATA SET IEF196I SYS1.SAPPRD2.DMP00002, IEF196I DATA WAS SPREAD OVER MULTIPLE VOLUMES IEF196I IGD101I SMS ALLOCATED TO DDNAME (SYS00003) IEF196I DSN (SYS1.SAPPRD2.DMP00002 ) IEF196I STORCLAS (DUMPS) MGMTCLAS ( ) DATACLAS (DUMPS) IEF196I VOL SER NOS= $PWK92,$PWK35 IEF196I IGD104I SYS1.SAPPRD2.DMP00002 IEF196I DDNAME=SYS00003 IEA611I COMPLETE DUMP ON SYS1.SAPPRD2.DMP00002 863 DUMPID=002 REQUESTED BY JOB (PBP2DIST) FOR ASIDS(005C,005B,005A) INCIDENT TOKEN: P1PLXSAP SAPPRD2 07/03/2014 19:33:41 SDRSN = 00200000 00000000 00000000 40000000 SOME STORAGE COULD NOT BE DUMPED RC=8 TASKS RESET DISPATCHABLE PRIOR TO DUMP COMPLETION ERROR ID = SEQ04165 CPU89 ASID005C TIME19.33.32.3 So did the system capture all dump content ? Manual says only Summary dump records are missing. Can you please confirm ? Also, how it can be avoid in future ?
Answer
If the dump was truly truncated, MSGIEA611I would NOT contain "COMPLETE DUMP" in its header. The z/OS MVS System Messages manual provides the following detail explanation for the text SOME STORAGE COULD NOT BE DUMPED RC=8
08 Not all of the data requested in a summary dump could be
contained in the central storage buffer or virtual storage
buffer.
Note: Even though some summary dump records might be missing,
IEA611I COMPLETE DUMP is issued when there are no other
data truncation reason bits set. This indicates that the
dump contains all of the virtual storage requested. Only
the summary dump records are missing, and these are
usually duplicated in the virtual storage dumped at a
slightly later time.
As you can see, there is no real loss of data, even if the summary dump is not available (with the exception of the trace table which is IN the dump).
This is because suspend summary dumps normally contain pageable storage, besides paged-in and DREF storage; and this pageable storage may be found in the rest of the taken SVC dump.
Nevertheless, is it possible to avoid a repetition of this situation?
The first portion of the SDRSN field indicates that during suspend summary dump processing, the virtual storage buffer filled up. This buffer is allocated in the DUMPSRV address space, in 31-bit high private
above the line. Currently, its size may be as large as approximately 128MB but the buffer is shared between dumps; so, a large number of dumps, running concurrently, may lead to depletion of the buffer.
As you can see, the only option to prevent its depletion would be taking a lesser number of concurrently running SVC dumps.
Historical Number
18239;49R;000
Was this topic helpful?
Document Information
Modified date:
03 September 2021
UID
isg3T1021050