/**********************************************************************/ /* Use this parmlib member on the DUMP system command for capturing */ /* the state of OMVS after you have detected a problem. Typically, */ /* if the system detects a problem it will take an appropriate dump */ /* by itself. When assistance is needed, this parmlib member could */ /* help you tailor the dumps to collect the proper information. */ /* */ /* Since multiple data spaces and address spaces may be dumped on */ /* each system, you will probably need to increase the amount of */ /* space needed to capture dumps. This can be done in your COMMNDxx */ /* parmlib member using the SET command like */ /* COM='SET SDUMP,MAXSPACE=1000M ' */ /* Your dump data sets will also have to be large enough to handle */ /* these dumps. */ /* */ /* This will dump the OMVS address space on all systems in the */ /* sysplex and include the LFS data spaces. The SYSZBP1 data space */ /* is automatically included. If this member is copied as IEADMCOE */ /* this command could be used to take the dump: */ /* */ /* DUMP COMM=(descriptive name of dump),PARMLIB=OE */ /* */ /* To include jobs on the system where the dump command is issued */ /* change JOBNAME=(OMVS) to include a list, e.g., */ /* JOBNAME=(OMVS,WJS1,WJS2), */ /* */ /* To include jobs on all other systems, change the REMOTE line, e.g. */ /* REMOTE=(SYSLIST=*('OMVS','WJS1','WJS2'), */ /* DSPNAME and SDATA on REMOTE says to use what was previously used. */ /* */ /* See the MVS Systems Commands book for additional information on */ /* parameters for the DUMP command. */ /* */ /* After the dump is taken, make sure that no messages were issued */ /* that indicate a partial dump was taken (your dump data set is too */ /* small) or that your MAXSPACE has been exceeded. */ /* */ /**********************************************************************/ JOBNAME=(OMVS), DSPNAME=('OMVS'.SYSZBPX2,'OMVS'.BPXFSCDS), SDATA=(CSA,SQA,RGN,TRT,COUPLE,XESDATA,GRSQ), REMOTE=(SYSLIST=*('OMVS'), DSPNAME,SDATA)