PARSEC Technical Information

User Tools

Site Tools

Trace:
how_to_send_a_vms_crash_dump_to_parsec_for_analysis

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
how_to_send_a_vms_crash_dump_to_parsec_for_analysis [2018/09/10 21:41] – lrickerhow_to_send_a_vms_crash_dump_to_parsec_for_analysis [2018/10/23 19:26] – <code>...</code> tweaks lricker
Line 11: Line 11:
 Whenever possible, //send the copied Dump File//, not the original System Dump File.  The reason for this is that, in copying the Dump File to its alternative, SDA augments dumped file identifiers (FID) with actual file-specifications wherever available, plus some additional information.  In other words, the SDA COPY command also includes the actions of the SDA COLLECT command: Whenever possible, //send the copied Dump File//, not the original System Dump File.  The reason for this is that, in copying the Dump File to its alternative, SDA augments dumped file identifiers (FID) with actual file-specifications wherever available, plus some additional information.  In other words, the SDA COPY command also includes the actions of the SDA COLLECT command:
  
 +<code>
   SDA> help copy   SDA> help copy
-  +
   COPY   COPY
-  +
        Copies the contents of the dump file to another file.        Copies the contents of the dump file to another file.
-  +
        Format        Format
-  +
          COPY  [/qualifier...] output-filespec          COPY  [/qualifier...] output-filespec
-  +
   SDA> help collect   SDA> help collect
-  +
   COLLECT   COLLECT
-  +
        Collect file identification to file name translation data on        Collect file identification to file name translation data on
        both OpenVMS Alpha and OpenVMS for Integrity servers, and process        both OpenVMS Alpha and OpenVMS for Integrity servers, and process
        unwind data only on OpenVMS for Integrity servers.        unwind data only on OpenVMS for Integrity servers.
 +</code>
  
 PARSEC recommends that you SFTP or FTP the //copied Dump File// to us for analysis, as this provides us with the full, contextual information from your VMS system.  Without this, several vital clues to your crash event may be missing.  See [[How To Capture a VMS Crash Dump]]. PARSEC recommends that you SFTP or FTP the //copied Dump File// to us for analysis, as this provides us with the full, contextual information from your VMS system.  Without this, several vital clues to your crash event may be missing.  See [[How To Capture a VMS Crash Dump]].
Line 63: Line 65:
 ''$ **DIRECTORY /FULL DUMPFILE_COPY_05122016.DMP;**''\\ ''$ **DIRECTORY /FULL DUMPFILE_COPY_05122016.DMP;**''\\
  
 +<code>
   Directory DSA2:[LRICKER.CRASH_ANALYSIS]   Directory DSA2:[LRICKER.CRASH_ANALYSIS]
-  +
   DUMPFILE_COPY_05122016.DMP;1              File ID:  (47086,142,0)   DUMPFILE_COPY_05122016.DMP;1              File ID:  (47086,142,0)
   Size:        95221/95328      Owner:    [STAFF,LRICKER]   Size:        95221/95328      Owner:    [STAFF,LRICKER]
Line 70: Line 73:
   Revised:     5-DEC-2016 13:23:18.67 (2)   Revised:     5-DEC-2016 13:23:18.67 (2)
   Expires:  ...%< snip >%...   Expires:  ...%< snip >%...
-  +
   File attributes:    Allocation: 95328, Extend: 11923, Global buffer count: 0,   File attributes:    Allocation: 95328, Extend: 11923, Global buffer count: 0,
                       No version limit, Contiguous best try                       No version limit, Contiguous best try
Line 76: Line 79:
   Record format:      Fixed length 512 byte records   Record format:      Fixed length 512 byte records
   Record attributes:  ...%< snip >%...   Record attributes:  ...%< snip >%...
-  +
   Total of 1 file, 95221/95328 blocks.   Total of 1 file, 95221/95328 blocks.
 +</code>
  
 To create that save-set (*.BCK) file with this entire dump-copy usefully saved in it, use a BACKUP command like this: To create that save-set (*.BCK) file with this entire dump-copy usefully saved in it, use a BACKUP command like this:
Line 89: Line 93:
  
 If you fail to do any of the above steps correctly, you’ll be burning a lot of wasted time preparing and FTP-transferring an “empty but very large dump file” to your crash dump support team! If you fail to do any of the above steps correctly, you’ll be burning a lot of wasted time preparing and FTP-transferring an “empty but very large dump file” to your crash dump support team!
- 
- 
how_to_send_a_vms_crash_dump_to_parsec_for_analysis.txt · Last modified: 2018/12/04 19:00 by lricker
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki