>I can tell you the intent. Each allocation of above-2G storage fits into
>one of 5 "should I include it in the dump?" categories --
>- like region (default for private)
>- like LSQA
>- like CSA (default for common)
>- like SQA
>- do not dump automatically
>
>The intent is to dump "like x" when 'x' is included. Things that are "do
>not dump automatically" are expected to be included explicitly (e.g.,
>LIST64, SUMLIST64) in a dump, when needed.
Dusting off this old thread:
I set a slip trap that included the TCPIP address space in the address spaces
to be dumped. TCPIPCS socket detail on that slip dump gives me:
TCPIP Socket Analysis
BLS18100I ASID(X'002B') 01F0_22800000 not available
The address is in hvcommon, according to rsmdata.
When I use a dump command (asynchronous to my slip trap) to just dump the TCPIP
address space, the same command formats out everything I want to see. Same dump
options on the system:
SDUMP- ADD OPTIONS (ALLPSA,NUC,SQA,RGN,LPA,TRT,CSA,SWA,SUMDUMP,
GRSQ),BUFFERS=00000000K,MAXSPACE=00000500M,
MSGTIME=99999 MINUTES,MAXSNDSP=015 SECONDS,
AUXMGMT=ON ,DEFERTND=NO
complete dump in both cases.
How come a slip dump does not dump common storage above the bar despite both
SQA and CSA being set?
Barbara
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
