For HVCOMMON, I would think that SDUMP should be turning on
the common storage bit in the dump record prefix, and IPCS should
be respecting that and allowing you to access the storage via any
ASID.
Big thanks (again) to Jim Mulder for looking at this. SDUMP does indeed
everything it should and
It would be easiest if you could send this dump somewhere
that I can access. Like opening a PMR and sending the dump, if
you have a license to do that. Or sending it to Dallas if you
have an ISV relationship there.
Thanks Jim, I have done so.
Barbara
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_2280 not available
The address
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
In 7676853980546110.wa.nitzibmgmx@listserv.ua.edu, on 03/11/2015
at 07:41 AM, Barbara Nitz nitz-...@gmx.net said:
How come a slip dump does not dump common storage above the bar
despite both SQA and CSA being set?
Did the IARV64 macro have DUMP=NO or XMFCTRL_XDUMP_NO?
--
Shmuel
On Sun, 28 Sep 2014 21:20:54 -0400, Peter Relson wrote:
It seems that the obtainer of the storage should know under what
circumstances it would get into SDUMP(X) -- since, in effect, that is
within the doc for obtaining the storage -- but that the user of a DUMP
command might not (thus the need
All of the LIKE options are well documented for IARV64.
In the z/OS 2.1 books, SDUMPX's SDATA CSA and RGN options have this
information (LSQA does not, and SQA's has an obvious type of mentioning
DUMP=LIKECSA instead of DUMP=LIKESQA, and RGN's is incomplete in
mentioning only SVCDUMPRGN=YES
On Fri, 26 Sep 2014 07:41:13 -0400, Peter Relson wrote:
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
Now what I still don't quite 'get' is how to dump everything
needed above the bar automatically. RGN does not seem to cover
that, so any program experiencing a problem would need to
explicitly specify ranges of storage above the bar in its
own dump invocation. Or am I missing something?
I can
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'
On Fri, 26 Sep 2014 13:59:43 +0200, Barbara wrote:
Thanks Peter, that certainly explains it.
+1
... even though I generally frown upon me too posts ;-)
Shane ...
--
For IBM-MAIN subscribe / signoff / archive access
On 9/26/2014 5:59 AM, Shane Ginnane wrote:
On Fri, 26 Sep 2014 13:59:43 +0200, Barbara wrote:
Thanks Peter, that certainly explains it.
+1
... even though I generally frown upon me too posts ;-)
Me too.
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El
And really, me too!!
Linda
Sent from my iPhone
On Sep 26, 2014, at 8:24 AM, Ed Jaffe edja...@phoenixsoftware.com wrote:
On 9/26/2014 5:59 AM, Shane Ginnane wrote:
On Fri, 26 Sep 2014 13:59:43 +0200, Barbara wrote:
Thanks Peter, that certainly explains it.
+1
... even though I generally
CD SET,SDUMP=(RGN,CSA,LPA),ADD,MAXSPACE=5000M
... probably inherited from something someone did before the last
millennium.
Does anyone have any other (21st-century) recommendations for improving
this?
I have set this:
CD SET,SDUMP=(ALLPSA,CSA,SQA,GRSQ,LPA,NUC,RGN,SUM,SWA,TRT)
In our
Ed Jaffe wrote:
I noticed our most important systems issue the following command in COMMNDxx:
CD SET,SDUMP=(RGN,CSA,LPA),ADD,MAXSPACE=5000M
Just only that? What about LSQA, NUC, PSA, SUMDUMP and other friends?
Beside MAXSPACE, what is the size of BUFFERS? (We got it at 8M)
... probably
Hello all,
As a DB2 v10 recommendation we have set out MAXSPACE to 1M (10GB).
We had to increase Central and Auxiliary (PAGE) storage in order to do
this. If a DB2 dump is taken things can get nasty storage-wise when running
with this recommended value.
Regards,
*Lucas Rosalen*
2014-09-25
On Thu, 25 Sep 2014 18:08:02 -0300, Lucas Rosalen wrote:
As a DB2 v10 recommendation we have set out MAXSPACE to 1M (10GB).
We had to increase Central and Auxiliary (PAGE) storage in order to do
this. If a DB2 dump is taken things can get nasty storage-wise when running
with this recommended
17 matches
Mail list logo
