> :>>I am trying to issue a tailored SVC dump and am finding that there are > :>many > :>>absolute storage records filling the dump - many more since zos/1.10 > > :>>I specify SDATA=(NODEFS,NOALLPSA,NOSQA) - what more do I need to specify? > > :> How did you determine that there are many absolute storage records? Did > :>you > :>count the number of records whose dump record prefix starts with 'DR2 A .' > > Yes. Also do a LISTDUMP and found more than x'05------' (80M) bytes described > in ABSOLUTE. > > USING SDUMPX directed to a DCB. > > By changing it to use LIST64 instead of SUMLIST64 and using SDATA=(,NOSUM) > reduced the ABSOLUTE to about 28M. > > The issue is that I try to allocate the output dataset to the size I need (as > it must be CONTIG) and found the amount of "overhead" storage went up quite a > bit from zos1.10.
The DRPX for SD, SV, CV, and DS records can contain the absolute address of the storage as well as the virtual address. SDUMP has provided the absolute address since z/OS 1.8. For SVC dumps, IPCS maps both the virtual and absolute addresses. LISTDUMP is telling you the amount of storage which is mapped as absolute, which includes the storage which is mapped as both virtual and absolute. So this number will be larger than the amount of storage which was dumped as absolute records. You can do VERBX SUMDUMP to determine the reasons that various areas were included in the SUMDUMP. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
