ADSM-L

Re: STK9740

1999-09-24 15:58:09
Subject: Re: STK9740
From: Clint Placette <Clint.Placette AT FDC-INVEST DOT COM>
Date: Fri, 24 Sep 1999 15:58:09 -0400
You right.

I got so dependent on my macros that I was not paying attention to
what I was doing.  The real twist was that ADSM appeared to have
accepted the volumes because I could see them.  Plus I was still
wiping the drool off my mouth from the new system.  I owe you a
coffee.

Thanks
Brain dead


______________________________ Reply Separator _________________________________
Subject: Re: STK9740
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> ("Robinson, 
Cris"
<Cris.Robinson AT LIBERTYMUTUAL DOT COM>) at INET
Date:    9/24/99 2:11 PM






       Clint -

       Did you label and checkin or just checkin?

       Checking in with the barcode command does not label the media.

       I would use the label command with the checkin if you haven't already:

       LABEL LIBVOLUME "LIBRARYNAME" SEARCH=YES LABELSOURCE=BARCODE
       CHECKIN=SCRATCH

       Good luck!

       CR

       __________________________________________________
       Cris Robinson
       Sr. Technical Analyst
       Enterprise Storage Management / ADSM
       Liberty Mutual Insurance
       Portsmouth, New Hampshire
       603.431.8400.54837
       mailto:cris.robinson AT libertymutual DOT com

               -----Original Message-----
               From:   Clint Placette [SMTP:Clint.Placette AT FDC-INVEST DOT 
COM]
               Sent:   Friday, September 24, 1999 1:41 PM
               To:     ADSM-L AT VM.MARIST DOT EDU
               Subject:        STK9740

               Hello,

               I just brought a secondy Library on line.  A stk 9740 with 9840
               drives.  I did an audit of the lib and all 170 volumes came up.
       I
               then issued a CHEKIN LIBV TEKWOLF VOLRANGE=000000,000169
       STAT=SCRATCH
       volume into
               scratches.

               Here is where it gets hairy.  I decided to due a database back
       to
       the
               new LIB.  What I got was the LIB went to each volume marking
       each
               volume to private (170).  It was trying to due a db backup but
       it
       kept
               getting this error ANR8355E I/O error reading label fo volume
       ### in
               drive  ##.

               Well I decide to call IBM they wanted me to audit the LIB
       again.
       This
               proved fruital because after the audit it blew away all the
       volumes.
               I bet you can't guess what I am doing right now.  Yes that's
       right I
               am auditing the LIB again.

               Can anybody help me on this.

               AIX 4.2.1
               ADSM 3.2.1.40
<Prev in Thread] Current Thread [Next in Thread>