Matt,
Under os390 TSM does not know how many tape drives it has, it just calls for a
tape resource when it wants one.
We have os390 TSM server with DFRMM as the tape manager, but the principle is
the same with dataset name prefix on the device class determining the
destination of the tape.
Basically we then use device mount limit and TSM scheduling to make the best
use of the available tape drives.
If you find that you are struggling to do this then you may need more drives.
John
"MC Matt Cooper (2838)" <matt.cooper AT amgreetings DOT com> on 05/21/2002
12:41:51 PM
Please respond to "ADSM: Dist Stor Manager" <adsm-l AT vm.marist DOT edu>
To: adsm-l AT vm.marist DOT edu
cc: (bcc: John Naylor/HAV/SSE)
Subject: yes/no tape question for os/390 server people
Hello,
I have been running TSM 4.1 on z/OS for a year and a half now,
(started on OS390 2.7). I wanted to take advantage of and follow the
standard usage of our tape systems so I set up the TSM tape system in a way
that I now question. I would like people to let me know if they are doing
things like I am or not. If you would like to explain what you do, ood but
please just let me know if I am out on my own with this. I am trying to
determine if it is worth my time to change things. It is a little odd but
here I go...
I set up my 6 9840 tape drives with two different DEVICE
definitions. I called one ONSITE9840 and the other OFFSITE9840. I did this
because our entire CA1 Tape handling and STK SILO handling is based on the
high level qualifier of the data set name on the first file of the tape.
So I gave the 2 device classes different high level qualifiers, told the CA1
and STK software what I was doing and the normal running production system
that put tapes in a vault pattern that has the offsite tapes go to our DR
site with all the other tapes needed at DR was taken care of. No other
special handling. It also took care of ejecting the tapes that were going
offsite from the tape Silo system. No extra handling. I did have to add a
step there to have TSM mark those tapes as OFSITE , that was it. I then
would have my tape COPYPOOL use the OFFSITE9840 and the disk backuppoool
migrate to the TAPEPOOL that used the ONSITE9840.
The problems that seem to come from this is TSM thinks it has
more tape drives than it does. SO TSM may start to do a disk to tape
migration but it really doesn't have the tape drives available, yet (because
they are busy making OFFSITE copies of backups). This of course makes
scheduling much more difficult. And it has gotten ugly at times with
server consolidations and the fact that I am running in ROLLFORWARD mode
with version 4.1 and the 5GB log. So I am wondering if my life would be
better if I really only defined to TSM the proper number of tape drives and
let it handle some of its scheduling affairs, and I wrote all the procedures
to handle the tapes coming and going affairs. (which of course will change
the playing field for my schedules....)
SO DO YOU SET UP YOUR TSM TAPE HANDLING ON OS390 z/OS LIKE THIS ?
Thanks
Matt
**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.
Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**********************************************************************
|
