Gosh, Bill, that's even better!
Now if we could just cut it down to zero steps...
---------------------------------
Mr. Lindsay Morris
Mr. Lindsay Morris
CEO, Servergraph
www.servergraph.com
859-253-8000 ofc
425-988-8478 fax
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Bill Boyer
> Sent: Friday, April 12, 2002 10:29 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: 3494 library swap out.
>
>
> Maybe more of a generic way that doesn't depend on any specific
> OS....use a
> SQL command:
>
> select 'checkout libv ' || trim(library_name) || ' ' ||
> trim(volume_name) ||
> ' checkl=no rem=no' from libvolumes
>
> and pipe this to a file. You can then run it in as a MACRO libr Lindsay
> suggests. You may have to SET SQLDISPLAYMODE WIDE to get it all
> on one line.
>
> This doesn't rely on cat....awk.....MSWord...or any utility. Just a TSM
> admin client.
>
> There's more than one way to skin a cat! :-) Whatever you're comfortable
> with. Myself, with going to different client sites with different
> systems, I
> just don't like to come to rely on a solution on a particular platform. No
> offense intended!
>
> Just my $.02 worth.
> Bill Boyer
> DSS, Inc.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Mr. Lindsay Morris
> Sent: Thursday, April 11, 2002 9:45 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: 3494 library swap out.
>
>
> I guess different people like different tools...I'm a command-line bigot.
>
> The idea of turning a list of volumes into a script is a very good idea.
> Here's a unix-ified way to do it for those who will, maybe faster:
>
> 1. Obtain a list of volumes (or stgpools, or...) into a file, say,
> "/tmp/vols"
> 2. cat /tmp/vols | awk '{print "checkout libv library_name $1 checkl=no
> rem=no"}' >/tmp/macro
> vol name is here ----^^
> 3. dsmadmc -id=... -pas=... -itemcommit macro /tmp/macro
> itemcommit means if one line fails, don't roll back the
> whole script
>
> Not trying to one-up you, Tab - people more comfortable with MS
> Word should
> use it.
> The idea is great. I often see people doing stuff like this manually, and
> it makes me cringe.
> Thanks for the post.
>
> ---------------------------------
> Mr. Lindsay Morris
> CEO, Servergraph
> www.servergraph.com
> 859-253-8000 ofc
> 425-988-8478 fax
>
>
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf
> > Of
> > Tab Trepagnier
> > Sent: Thursday, April 11, 2002 6:56 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: 3494 library swap out.
> >
> >
> > Geoffrey,
> >
> > Whenever I have to do similar operations on lots of volumes, I
> use my word
> > processor's (MS Word in this case) mail merge feature to help. The
> > sequence goes like this.
> >
> > 1. Obtain a list of volumes to be processed. If the volume name is the
> > only thing that will change, you can save to a text file. But
> text files
> > only accommodate one variable. If more variables (fields) are
> needed, use
> > the native WP doc format.
> >
> > 2. Select the file from step 1 as the data source.
> >
> > 3. Create the master document with the desired command line like:
> > checkout libv library_name [volume] checkl=no remove=no
> >
> > where "volume" is the "merge field" to be used for the final document.
> >
> > 4. Merge the data. You will end up with a document that has a line from
> > step 3 for each volume.
> >
> > 5. Because that document will be in the native WP format, do a Save
> > As...text of the document.
> >
> > 6. Reopen the text version of the document. You will have a script.
> >
> > 7. Paste that text document's contents into the text entry window of the
> > Create Script page of the TSM web client. The final result will be a
> > server script consisting of the command from step 3 for each volume.
> >
> > 8. Execute the server script in TSM.
> >
> > I know this sounds a bit complicated, but once you've done it a time or
> > two, you can create in less that five minutes scripts that process
> > thousands of volumes.
> >
> > This technique was vital when I was doing our data reorg after
> the library
> > upgrades and I had to Move Data the contents of hundreds of tapes.
> >
> > Good luck.
> >
> > Tab Trepagnier
> > TSM Administrator
> > Laitram Corporation
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > "Gill, Geoffrey L." <GEOFFREY.L.GILL AT SAIC DOT COM>@VM.MARIST.EDU> on
> > 04/11/2002
> > 12:34:16 PM
> >
> > Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> >
> > To: ADSM-L AT VM.MARIST DOT EDU
> > cc:
> > Subject: 3494 library swap out.
> >
> >
> > On Monday IBM will be removing a leased 3494 and installing a
> replacement
> > 3494. The library is shared with MVS but MVS has it's own set
> of tapes and
> > exits ignore my tapes(TSM 4.2.1.9 on AIX 4.3.3) when they are inserted.
> >
> > It's been sugested I "checkout" all of my tapes, some 800 or
> so, probably
> > with a remove=no since a 10 slot I/O port would slow things
> down. IBM says
> > they need to remove all the tapes so they can re-level the library once
> > they
> > put it together.
> >
> > So now questions: (I am not concerned with the MVS side of things since
> > someone else takes care of that.)
> >
> > Do I really need to do this?
> >
> > If yes, is there an easy way to do this or amI going to have to struggle
> > through it?
> >
> > How about getting them back in/available?
> >
> > Should I be doing any TSM inventory?
> >
> > If anyone ahs gone through this or has suggestions please, please send
> > them.
> >
> > Thanks,
> >
> > Geoff Gill
> > TSM Administrator
> > NT Systems Support Engineer
> > SAIC
> > E-Mail: gillg AT saic DOT com <mailto:gillg AT saic DOT com>
> > Phone: (858) 826-4062
> > Pager: (877) 905-7154
> >
>
|
