HP3000-L Archives

September 2013, Week 1

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Curiosity Question on Memory Dump
From:
"Johnson, Tracy" <[log in to unmask]>
Reply To:
Johnson, Tracy
Date:
Thu, 5 Sep 2013 13:42:32 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (1 lines) 
When the disk dump location was mentioned yesterday it also inadvertently solved the problem.



In my disk to disk full back up routine, I purposely avoid backing up the back ups with a negative ONVS option (;ONVS=-BACKUP_SET) where my backups are located.  (It may occur to the dear reader it would be rather redundant otherwise.)



That being said, it appeared the back up was crashing the machine at the same place every time.  After yesterday's revelation, I did a quick :DSTAT ALL and remembered the DUMP_SET I had made some time previously.  I added another negative for DUMP_SET to the back up job and the disk to disk backup stopped crashing the system.  



Problemm solved.



It doesn't appear to explain were my tapeless DUMPs were going because a LISTF only shows the one huge file on the DUMP_SET was Accessed yesterday, but was Modfied last October.  Which is probably the first and last time I attempted to learn how to use the file.  I would think if DUMP to disk were working, it would have been modified yesterday.  



Unless it is one of those special things where the Modify portion of the label doesn't get changed after a new DUMP?  



Perhaps only the BLDDUMP program alters it?



It shows as a protected file with CR only access.  So I can't purge it.  I made that bed now I have to sleep in it, unless I go to the BLDDUMP manual and re-learn it.





Tracy Johnson

Office (757) 766-4318

[log in to unmask]





> -----Original Message-----

> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On

> Behalf Of Lars Appel

> Sent: Thursday, September 05, 2013 3:39 AM

> To: [log in to unmask]

> Subject: Re: [HP3000-L] Curiosity Question on Memory Dump

> 

> Mark Ranft wrote:

> > Do you have a volume set called DISKDUMP_VOLUME_SET?

> 

> You may also check the disk dump setup this way, as far as I recall...

> 

>   :RUN BLDDUMP.HP36375.TELESUP

>   blddump > LIST

>   blddump > EXIT

> 

> If you don't have the BLDDUMP program, AutoRestart/iX is not installed.

> 

> Lars.

> 

> * To join/leave the list, search archives, change list settings, *

> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *



* To join/leave the list, search archives, change list settings, *

* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2