× 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.



Hi Rob

that was my first thought but that did not turn out to be the case.

I'm still looking at this but I did track down the movement by reading the
journal for file QUSRBRM/QA1AMM which gave me the time the location changed
for the volume in question. I then managed to find the event in the BRMS
log by browsing the *MED entries (DSPLOGBRM *MED)

As it turned out the move to the *HOME location was caused by another
system in the BRMS network using a volume named the same to do a restore.
After the restore the volume was moved to the *HOME location on the system
that owned the volume.

Just for curiousity sake, the sequence of events was:
- Save was done to virtual tape on SYSTEMA using BRMS
- Virtual tape file was transferred to SYSTEMB
- Restore done using native commands on SYSTEMB (SYSTEMB and SYSTEMA are in
same BRMS network)
- SYSTEMB moved volume to *HOME location after restore and SYSTEMA voume
detaisl were updated.



On Thu, Sep 29, 2016 at 12:31 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

You don't have any move policy assigned to that do you?

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





From: Evan Harris <auctionitis@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/27/2016 06:07 PM
Subject: BRMS When was Location changed for volume
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Hi

I had a backup temporarily halt because a virtual tape had the wrong
location assigned.

I've been trying to figure out how the volume got assigned to the *HOME
location - normally it's location is DISK - but can't find any indication
of where or how this came about.

Is there a table or log I can review to see how this might have come about
?

No suggestion that BRMS has misbehaved, just trying to figure out how the
change happened.

--

Regards
Evan Harris
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.