Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Recovering DFSMShsm after an abnormal end z/OS DFSMShsm Implementation and Customization Guide SC23-6869-01 |
|
When an error causes DFSMShsm to end abnormally, SETSYS SYS1DUMP is the DFSMShsm default and causes a dump to be written to a SYS1.DUMP data set. SYSUDUMP, SYSMDUMP, or SYSABEND DD are other options, but their use is strongly discouraged. You can analyze the dump to determine how much of the current function has been processed and how much work is waiting to be processed. You might need to reschedule the function that was running when the abnormal end occurred. If you do not include a SYSUDUMP, SYSMDUMP, or SYSABEND DD statement, print and edit the DFSMShsm log to determine and re-create the events that caused the abnormal end. You can use the TRAP command to isolate the situation that has caused the abnormal end. |
Copyright IBM Corporation 1990, 2014
|