Don,
I have also recently been looking into this issue via a PMR and had a very
similar answer to the one given to John below.
I think the point is when the DRM PREPARE command is run one of these
messages is logged for every single generated volume name - in our case
that is about 1600 messages every day. I (and I'm sure that John too) had
read and understood the manual that the plan contains volume names with
markers that we would need to do something about in the event that a
disaster occurred and the plan would be brought into use.
What use then of 1600 messages in an activity log that has been trashed?
One message each day reminding that the plan needs editing would suffice!
If the activity log is cluttered up with irrelevant messages it just makes
it harder to spot the messages that are important, warnings or otherwise
(as well as the wasted space).
Thanks. Regards, Sheelagh
------------------------------------------------------------------------------
Sheelagh Treweek Email: sheelagh.treweek AT oucs.ox.ac
DOT uk
Sheelagh Treweek Email: sheelagh.treweek AT oucs.ox.ac
DOT uk
Oxford University Computing Services Tel: +44 (0)1865 273205
13 Banbury Road, Oxford, OX2 6NN, UK Fax: +44 (0)1865 273275
------------------------------------------------------------------------------
> From owner-adsm-l AT VM.MARIST DOT EDU Wed Aug 27 18:10:56 1997
> From owner-adsm-l AT VM.MARIST DOT EDU Wed Aug 27 18:10:56 1997
> Mime-Version: 1.0
> Date: Wed, 27 Aug 1997 12:53:17 -0400
> From: Donald Moxley <moxley AT US.IBM DOT COM>
> Subject: Re: PREPARE ANR6920W errors
> To: ADSM-L AT VM.MARIST DOT EDU
>
> >I think I need some help. Whenever I pass the DRM PREPARE command
> >my activity log has an entry like this for every tape volume:
> >08/25/97 18:17:47 ANR6920W PREPARE: Generated replacement volume name
> > SAP001@ is not valid for device class CARTRIDGE.
> John, the message is warning you that the recovery plan has generated names
for
> 'replacement'
> volumes in your storage pools that are not legal for the device class. (In
this
> case the names are
> longer than 6 characters.) At recovery time, the '@' can serve as an eye
> catcher for where new
> volume names need to be inserted. Another solution is to set maxscratch
greater
> than 0 and use
> scratch tapes. Bottom line is, you are not doing anything 'wrong'.
>
> Don Moxley, IBM Storage Systems Division
|
