SYSDUMP.DMP - retaining contents of

[John A. Beard]

Hi John,

Thank you for your input...

Where should we apply the ANAL/CRASH COPY cmmand in the startup sequence... site independent procedures or simply insert it in he begining of systartup_vms.com .

We backup everything to a newtwork storage system (retention policy by default set to 365 days), so once we were to get a copy of the dump file we can delete the copy without hogging disk space.

This is the last question I have on the subject and I would like to thank everyone for their very detailed and clear responses...you guys are and endless source of useful information

[Volker Halle]

John,

it is suggest to use the CLUE$SITE_PROC method to copy the dumpfile during startup. This is the offically recommended method to save dumpfiles.

Recommended method:

Create an SDA procedure that includes the COPY command
Ensure the COPY command is the last command
Define logical name CLUE$SITE_PROC (/SYSTEM)
If using DOSD, ensure disk is mounted and logical name CLUE$DOSD_DEVICE defined

Possible difficulty
If data disks not mounted, collection may not work
May prefer to delay copy, but will lose dump with another crash
Do separate collection with COLLECT /SAVE (I64 only)


Using this method also prevents the dumpfile from being copied on every boot.

Volker.

[Volker Halle]

John,

here is a pointer to the presentation of the OpenVMS engineer, who is mainting this part of OpenVMS:

http://de.openvms.org/TUD2006/19_Making_the_most_out_of_a_system_crash.pdf

Consider this information to be the ultimate resource about system dumps. This presentation is from 2006, but it's the best you can get without going to an OpenVMS Bootcamp like event yourself.

Volker.

[John A. Beard]

Excellent resonses to my questions..thanks folks.