Filter
Top Products
392 VM/HSC 6.0 System Programmer’s Guide
1st ed., 6/30/04 - 312579601
What to do When a Dump Occurs
When a VM HSC dump occurs, it is sent as a CLASS V spool file to the virtual machine
defined by the current DUMPOPTS setting. Dump files are large and can have a negative
impact on system spool space; they should be processed as soon as possible after they
occur.
The following steps should be taken when a dump occurs:
1. Move the CONSLOG and dump spool files to the dump processing machine’s virtual
reader.
2. Note the reason for the dump.
3. Load the CONSLOG and dump onto MAINTSTK’s IPCS disk.
4. Call StorageTek Software Support.
5. Move requested material to tape and ship to StorageTek.
Move Dump and CONSLOG to Dump Processing Machine’s Virtual Reader
If no DUMPOPTS command had been issued, then the dump will be found in STKACS’s
virtual reader.
Move it to the appropriate machine’s virtual reader by issuing the following command
from STKACS’s virtual console:
CP TRANSFER RDR CLASS V TO userid
If the initial settings of CONSLOG were in effect, then the CONSLOG will be found in
STKACS’s virtual reader as a class C PRT file with the name SLS.CONSOLE.LOG.
Move it to the same machine’s virtual reader by issuing the following command from
STKACS’s virtual console:
CP TRANSFER RDR CLASS C TO userid
Note Reason For Dump
Make a note of the reason the dump was created. If the dump was due to an ABEND, then
the ABEND code and reason code are kept in the spool file’s NAME and TYPE fields.
Issue the following command from MAINTSTK’s virtual console to display this
information:
QUERY RDR CLASS V ALL
Below is an example of the response for a dump taken due to an ABEND with a user
ABEND code of 1096 and a reason code of 4500450.
ORIGINID FILE CLASS RECORDS CPY HOLD DATE TIME NAME TYPE
STKACS 0074 V DMP 00001285 001 NONE 02/27 18:23:46 U1096!4500450