> I saw Barbara's note about including the dataspaces belonging to OMVS, but
> haven't seen a "complete" generation deck (or significant excerpt) from her
> yet.
You've asked for it:
AMDSADMP IPL=D3390,VOLSER=xxxxxx, +
REUSEDS=ALWAYS,IPLEXIST=YES, +
DUMP=('DSP OF ASID(ALL) ALSO PAGETABLES OF DATASPACES +
ALSO SP(ALL) IN ASID(ALL) +
ALSO HIGH VIRTUAL IN ASID(ALL)'), +
MINASID=ALL, +
DDSPROMPT=NO, +
OUTPUT=(Dyyyy,MVSR.SADMP), +
CONSOLE=SYSC
END
We had been running with this and even taking a few sadumps. A heavily
(over-)used 8GB lpar took about 10 minutes to 3 volsers via autoipl/sadump. The
beauty of the above is that it works on autoipl with no operator intervention
required (you know, those 30 minutes operators take to find the correct
document, read through it and do what it says?). The MVSR.SADMP is a historical
relict and had caused me some grief on an sadump restart. Check the archives,
at that time we discussed why it would be better to use sys1.sadmp.
And I see that we were better than system test - we did specify HIGH VIRTUAL
:-) I just wanted to avoid software supports' constant 'The data are not in the
dump' arguments by specifying everything and then proving to them that they
have no clue where to look. So I made it easy for me and just specified ALL for
just about everything.
Barbara
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
