×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I agree with Rob's comment below and I was always told not to use the MOVMED(*YES) parameter on the STRMNTBRM command because it may do unpredictable things. So I created a separate job to run the MOVMED process after all systems have completed BRMS activities.
"Perhaps you only want to use the MOVMED(*YES) option on the day when you are ready to physically remove the tapes from the library."
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vincent Forbes
Sent: Wednesday, June 19, 2013 11:07 AM
To: Midrange Discussion
Subject: BRMS moving
I am having trouble with BRMS moving. I get expired tapes, move them to TAPMLB01, change them {CHGMEDBRM} to have a new expiry date & move policy {DAILYSAVES}. The backup picks one of the tapes loaded works fine.
It gets a CPA401E "Library device storage slots full (C R)". Only "C" works. The tape drive is a 3573/040 with 12 slots & only 6 are used. After this, all of the tapes in TAPMLB01 are moved to various locations.
I want the tapes to remain in TAPMLB01 for the week. What am I missing?
Vincent
V6R1M0 Change System Policy
Type choices, press Enter.
Media policy . . . . . . . . . . . . . . DAILYSAVES Name, F4 for list
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.