HP3000-L Archives

November 2000, Week 3

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:
From:
Goetz Neumann <[log in to unmask]>
Reply To:
Goetz Neumann <[log in to unmask]>
Date:
Mon, 20 Nov 2000 03:31:53 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
Dennis Heidner wrote:
>
> This would not be a good idea.   For two reasons.

I have to respectfully disagree and agree at the same time:

> First,  you would potentially loose one of the major features of
> Autorestart, I.E,  memory dumps to disk.  I don't believe that disk dumps
> can span across physical disk drives.  Currently the LDEV1 can only be 4GB,
>  the OS uses (roughly) 2-3GB of disk space,  this would mean that after
> leaving space for transient, log files, some expansion, you'd only have a
> couple of hundred megabytes for the dump file.

You can build the DISKDUMP.TELESUP group on the
MPEXL_SYSTEM_VOLUME_SET, and diskdump files can span
multiple disks/volumes w/o problems. They would not
need to reside on LDEV 1.

But:

> Second, after building or modifying the dump file, you need to do a VSCLOSE
> and VSOPEN.  This is not something you want to do to the system volume set.
>   (Can you say system abort.....)

Since the only way to do a VSCLOSE of the MPEXL_SYSTEM_VOLUME_SET is
a =SHUTDOWN, any changes to your dump-to-disk files would require
extra downtime, which is not very practical.

HTH,
Götz.

ATOM RSS1 RSS2