ADSM-L

Re: Del Volh t=dbs is not working.

2002-09-10 01:33:08
Subject: Re: Del Volh t=dbs is not working.
From: "Mark D. Rodriguez" <mark AT MDRCONSULT DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 10 Sep 2002 00:31:22 -0500
Joshua Bassi wrote:

It should be 'del volh t=dbb todate=-1'


--
Joshua S. Bassi
IBM Certified - AIX 4/5L, SAN, Shark
Tivoli Certified Consultant - ADSM/TSM
eServer Systems Expert -pSeries HACMP

AIX, HACMP, Storage, TSM Consultant
Cell (831) 595-3962
jbassi AT ihwy DOT com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Mark D. Rodriguez
Sent: Sunday, September 08, 2002 3:01 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Del Volh t=dbs is not working.

Hi,

I just upgraded a server from 4.1.1 to 5.1.1.4 ( actually went 4.1.1 ->
5.1.0.0 -> 5.1.1.0 -> 5.1.1.4 ) on a W2K server.  After completing the
upgrade I am trying to delete the old DBS volumes ( made while at
4.1.1)  since they are no longer applicable.  I am using the following
command:

del volh t=dbs todate=-1

This should delete 2 volumes, however none are deleted.  Has anyone else
seen a similar problem?  Any ideas on how to delete these volumes?

Thanks in advance for any help you can offer.

--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc.

========================================================================
=======
MDR Consulting
The very best in Technical Training and Consulting.
IBM Advanced Business Partner
SAIR Linux and GNU Authorized Center for Education
IBM Certified Advanced Technical Expert, CATE
AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
Red Hat Certified Engineer, RHCE
========================================================================
=======


Joshua,

Thank You for your response.

Actually I am using the correct command since I am trying to delete
volumes that have DB Snapshots on them.  I have determined that the
problem is similar to one that existed in the past with volumes of type
DBB.  It is related to the "Series Number", for some reason during the
migration ITSM has reset the "Series Number" so that may subsequent ITSM
5.1.1.4 DB Snapshot got assigned "Series Number 1" while my older TSM
4.1 DB Snapshot "Series Number" where much higher values.  ITSM in its
infinite wisdom has decided not to let you delete a volume with a higher
"Series Number" than the current one.

I figure I will have to call Tivoli Support for this one, but I haven't
had time yet.  It's not really a show stopper it simply has stranded a
couple of volumes.

However, if anyone has ever fixed this problem in the past I would like
to hear how they did it.

--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc.

===============================================================================
MDR Consulting
The very best in Technical Training and Consulting.
IBM Advanced Business Partner
SAIR Linux and GNU Authorized Center for Education
IBM Certified Advanced Technical Expert, CATE
AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
Red Hat Certified Engineer, RHCE
===============================================================================

<Prev in Thread] Current Thread [Next in Thread>