BRMS, TS3100 and being totally ridiculous - RESOLVED

We have confirmed that IBM does NOT have a solution to this issue.

After repeated observations we determined the following:

1. Run: WRKMEDBRM LOC(TAPMLB02) and determine what media needs to be removed from the TS3100 based on creation date.
2. Remove the media identified in step one above from the TS3100.
3. Run tape movement: MOVMEDBRM MOVPCY(TMAG2IMTN) LOC(TAPMLB02)

Discussion:

The tape movement routine will move the tapes in the BRMS database (desired) but will not attempt to eject the tapes because it knows that they are NOT in the TS3100 (TAPMLB02).

Problem kinda solved.

Jerry

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Draper
Sent: Friday, June 05, 2009 12:44 PM
To: Midrange Systems Technical Discussion
Subject: BRMS, TS3100 and being totally ridiculous

The lack of integration between IBM's BRMS and the IBM TS3100 tape magazine/drive (24 slots) makes for an awkward system that cannot be automated.

BRMS is setup with a move policy that runs on Friday mornings. We move tapes once per week. Eligible tapes need to have their locations changed in the BRMS database from TAPMLB02 to OFFSITE. A movement report needs to tell the operator which tapes to remove from the system.

Wouldn't it be nice if it worked seamlessly?

Running tape movement causes a tape error because only one tape can be "ejected" from the TS3100 at a time. You just can't move tapes in BRMS without the system trying to eject the tapes.