My impression is to keep all the data on DASD except HSM data (backup,
ML2) and very few ad-hoc backups.
I ve got the impression many years ago and still see no good reason to
change it.
My other impression is it's simpler to change gazillion (usually less)
of JCL jobs to explicitly point datasets to DASD than using TMM.
Of course virtual tape reliefs many pains of tape, but keeping things in
old way is not good for the future.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 2019-01-30 o 15:03, John Benik pisze:
I can't let this go. Several months ago I asked the question about determining
what tape data should reside on Dasd instead?
The impression I got was put everything to disk and let HSM handle it.
Unfortunately that solution won't work for us so I continue to try to find ways
to help us determine what tape data should be on disk instead. Yesterday in a
conversation I had with my boss he mentioned that there was a Tape Mount
Management Cookbook that basically had step by step instructions to help
determine where the data should reside. It is my belief through using volume
mount analyzer or mountmon I will be able to go after what I would call low
hanging fruit and change them to disk. We have over 1 million tape volumes in
our prod environment so this is a rather large undertaking as this number does
not include HSM tape. If anybody knows where I can find the Tape Mount
Management Cookbook that would be greatly appreciated. Or if somebody has
some suggestions on how to best attack this that would be great.
Our tape environment consists of one DLM 8100 specifically for HSM
and two DLM 8100's configured as Manual Tape Libraries used for our General
Purpose tape.
======================================================================
Jeśli nie jesteś adresatem tej wiadomości:
- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać
tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza)
tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać
karze.
mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st.
Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237,
NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
01.01.2018 r. wynosi 169.248.488 złotych.
If you are not the addressee of this message:
- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have
printed out or saved).
This message may contain legally protected information, which may be used
exclusively by the addressee.Please be reminded that anyone who disseminates
(copies, distributes) this message or takes any similar action, violates the
law and may be penalised.
mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital
City of Warsaw, 12th Commercial Division of the National Court Register, KRS
0000025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN
169,248,488 as at 1 January 2018.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
