|
What you are suggesting is what I consider "best practices". What this--
requires is that you have the following installed:
5770BR1 1 5101 BRMS-Network Feature
I do not think you need this also
5770BR1 2 5102 BRMS-Advanced Functions Feature
See the STRBALBRM command. It has ways of setting "reserves" and what not
and then doing some automatic balancing. If the systems are up and running
then balancing is no big deal. LparA can talk to LparB and borrow tapes
from it. Even if you are doing a restricted state save on LparA it can
fire up enough comm just to talk to LparB and borrow tapes if need be. The
rub is when both LparA and LparB are down then there's no way for LparA to
fire up comm on LparB to borrow tapes. This is why you do the balancing.
Works great! Been doing this for years on our VTL and on our physical
tape library long before that.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Steve McKay
Sent: Friday, April 17, 2020 2:29 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Sharing VTL "tapes" in BRMS
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.
All -
I have 2 V7R3 systems using BRMS and be sharing a single virtual tape
library.
How do I configure BRMS to allow them to share the "tapes" in the library?
Or do I have to set aside a group of tapes for each system?
There are 600 tapes in the VTL and I would like to configure the 2 systems
so that they each can use any expired tape available.
Thanks,
Steve McKay
(205) 585-8424
samckay1@xxxxxxxxx
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.