IBM BRMS for i

 View Only

 Issue Removing Unused Media Volumes

Richard Weber's profile image
Richard Weber posted Fri December 06, 2024 02:52 PM

I am working in a BRMS network of systems and I am trying to clean up/remove old unused media volumes from our inventory.  I have run across some that I can't do anything with because there is a conflict of which system in the network they belong to. 

In other words, when I try to remove a volume on system A, I get the message: 

Volume I00001 cannot be used at this time.         
Volume I00001 has been rejected due to reason code 07.

07 Volume I00001 is owned by system B.

Conversely, when I try to remove a volume on system B, I get the message: 

Volume I00001 cannot be used at this time.         
Volume I00001 has been rejected due to reason code 07.

07 Volume I00001 is owned by system A.

This conflict comes up for any option: Change, Remove, Move, Expire, etc.

I would appreciate suggestions to resolve this.

Rick Weber

CitiTrends 

Rich Malloy's profile image
Rich Malloy IBM Champion posted Thu December 19, 2024 11:27 AM

Hi Rick

I've had this same problem!!!  Amazing how this is NOT supposed to happen at all...A year or so ago I was talking to one of the BRMS developers from Fortra - they do have a tool to fix the owner but they wouldn't volunteer it until a support ticket came in for this. I didn't call but I did discover that if you force a sync from the central system the owner would update......Having said that, I wrote a utility that would compare the media owner based on what the central system believed vs what the other systems in the network thought. This does involve 3 part sql and updating a brms table though..if you're interested, I can send it you

Richard Weber's profile image
Richard Weber posted Thu December 19, 2024 04:03 PM

Thanks for your reply, Rich.  I also opened a ticket with IBM and received the response below.  I used the STRDFU suggestion for the control groups with a few tape issues and wrote an SQL for the ones with a lot of tapes.  It worked well and I cleaned up the inventory.

"Unfortunately it looks like something was done to create a lot of mismatches in your BRMS network. There are a couple of options to fix this, and the first one would be used typically when only a couple of tapes are this way. Only do this for volumes which are *EXP or have passed the *expiration date.

Option 1)

a. STRDFU <enter>

b. Update data using temporary program

Data file . . . . . . . . . qa1amm

Library . . . . . . . . . qusrbrm

c. Volume Serial Number: xxxxxx

d. change the System ID:       to what you you want it to be so both systems see the same thing

e. F10

f. repeat for all volumes

Option 2)

a. Take apart BRMS network

b. Fix volumes so that they are owned by correct system

c. Put systems back into network"

Rich Malloy's profile image
Rich Malloy IBM Champion posted Thu December 19, 2024 04:17 PM

Glad you got it working Rick. Because this happened to me a couple of times, I just ended up automating it and have it as a scheduled job to run a3x a week so I don't do it anything manually for this. (it audits for the discrepancy and then fixes it)  Hope it behaves after you fixed it.. lol. Thanks