HP3000-L Archives

July 1998, 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:
Ron Burnett <[log in to unmask]>
Reply To:
Ron Burnett <[log in to unmask]>
Date:
Fri, 17 Jul 1998 08:52:22 EST
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
Keven Miller wrote:

> I know this has been said before.
>
> I believe on the classic, a 2nd, 3rd... media request on a restore/store
> not only printed a message on the console, but it went into the reply
> table as well.
> You could do a RECALL to see that your tape job is waiting for the next
> reel/media.
>
> Now on iX, its only a console message.
> I wish its was back in the reply table!

A very loud and wishful ME TOO!  I manage two HP3000s and do a
great deal of backup and restore work from remote locations (with
tapes pre-loaded by operators, in one or more of DDS1, DDS3 and
open reel drives).  The lack of a recallable mount request
causes real problems.  For example, a 'mount next reel' request
on a DDS1 tape, in my particularly environment, would nearly
always mean the tape drive was not compressing the way it was
expected to .... I would confidently abort the backup, force
compression on, put the tape back online and restart.  With
an open reel tape, it would nearly always mean somebody left
a huge stack dump deferred in the output printer queues ... and
I could equally confidently abort the backup process, purge or
copy somewhere else the big file, put the tape back online and
start again.

There is a definite need for these messages to be recallable.
How about it, HP?

Ron Burnett
[log in to unmask]

ATOM RSS1 RSS2