Differences

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

--- how_to_send_a_vms_crash_dump_to_parsec_for_analysis [2018/09/10 21:41] – lricker
+++ how_to_send_a_vms_crash_dump_to_parsec_for_analysis [2018/10/23 19:35] – <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:
-  SDA> help copy
+<code>
+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
-       both OpenVMS Alpha and OpenVMS for Integrity servers, and process
+     Collect file identification to file name translation data on
-       unwind data only on OpenVMS for Integrity servers.
+     both OpenVMS Alpha and OpenVMS for Integrity servers, and process
+     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]].
@@ Line 63: / Line 65: @@
 ''$ **DIRECTORY /FULL DUMPFILE_COPY_05122016.DMP;**''\\
-  Directory DSA2:[LRICKER.CRASH_ANALYSIS]
+<code>
+Directory DSA2:[LRICKER.CRASH_ANALYSIS]
-  DUMPFILE_COPY_05122016.DMP;1              File ID:  (47086,142,0)
-  Size:        95221/95328      Owner:    [STAFF,LRICKER]
+DUMPFILE_COPY_05122016.DMP;1              File ID:  (47086,142,0)
-  Created:     5-DEC-2016 13:17:34.72
+Size:        95221/95328      Owner:    [STAFF,LRICKER]
-  Revised:     5-DEC-2016 13:23:18.67 (2)
+Created:     5-DEC-2016 13:17:34.72
-  Expires:  ...%< snip >%...
+Revised:     5-DEC-2016 13:23:18.67 (2)
+Expires:  ...%< snip >%...
-  File attributes:    Allocation: 95328, Extend: 11923, Global buffer count: 0,
-                      No version limit, Contiguous best try
+File attributes:    Allocation: 95328, Extend: 11923, Global buffer count: 0,
-                      Backups disabled                       <<<--- that file attribute...
+                    No version limit, Contiguous best try
-  Record format:      Fixed length 512 byte records
+                    Backups disabled                       <<<--- that file attribute...
-  Record attributes:  ...%< snip >%...
+Record format:      Fixed length 512 byte records
+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:
@@ 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!