Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

BRMS media movement

252 views
Skip to first unread message

mbmulkey

unread,
Oct 3, 2001, 6:49:37 PM10/3/01
to
I seem to have a problem with BRMS and the VFYMOVBRM command. When
returning media from the vault, if I try to verify the media movement from
the "Verify Media Moves' screen, I get the following cpf messages.

CPF67D2 Cartridge does not exist, followed by
CPF67AB Cartridge not added

I have tried using the ADDTAPCTG command first, to get the tape into the
unit, as well as just inserting the tape in the import slot thinking that
BRMS would check for it there. My only recourse is to use option 8 from the
WRKMEDBRM screen, and then delete the entry from the VFYMOVBRM screen.

By the way, I have no problems with media being moved from the unit going to
the vault.

I would appreciate any input.

mb mulkey

MrDuck

unread,
Oct 3, 2001, 9:33:44 PM10/3/01
to
mbmulkey wrote:

What version/release of BRMS and OS400 are you on? BRMS gets to be very
picky if you're not up to snuff on all PTF's. Also, what type of library
hardware are you on (we, for example are on 3494 robots with 3590 drives).

MrDuck
--
From there to here
from here to there
funny things are everywhere!
--Dr.Seuss

mbmulkey

unread,
Oct 4, 2001, 12:21:40 PM10/4/01
to
5769ss1 is at 4.5
5769br1 is at 4.4
The library unit is a 3570 magstar tape unit, model b11 (19 slots plus 1
import slot, and 1 reader)
I've had IBM out on several occasions, for hardware related issues and had
the micocode updated. I would assume they would have insured the PTF levels
were current. When I talked to level 2 support about it, (over a year ago)
they said. "That's not supposed to happen." and that's as far as that went.

Obviously the problem is more of an inconvenience than anything, and I have
been able to deal with it for years now. When I recently discovered this
newsgroup I thought I would pose the question in the event someone had had
a similar problem and new of a simple fix.


"MrDuck" <miste...@earthlink.net> wrote in message
news:Y%Ou7.395$2p1....@newsread2.prod.itd.earthlink.net...

MrDuck

unread,
Oct 4, 2001, 3:46:46 PM10/4/01
to
mbmulkey wrote:

> 5769ss1 is at 4.5
> 5769br1 is at 4.4
> The library unit is a 3570 magstar tape unit, model b11 (19 slots plus 1
> import slot, and 1 reader)
> I've had IBM out on several occasions, for hardware related issues and had
> the micocode updated. I would assume they would have insured the PTF
> levels
> were current. When I talked to level 2 support about it, (over a year
> ago) they said. "That's not supposed to happen." and that's as far as that
> went.
>
> Obviously the problem is more of an inconvenience than anything, and I
> have
> been able to deal with it for years now. When I recently discovered this
> newsgroup I thought I would pose the question in the event someone had
> had a similar problem and new of a simple fix.
>
>

Sometimes, the answer is the one that you really don't want to hear. If
you don't press IBM for an answer or final solution, ESCALATE! I'd be
asking for a Duty Manager at Rochester by now if this didn't get resolved.
Failing that the local IBM branch should be notified as well.

The other reason I ask about the release, level, and what hardware you're
using is that IBM will typically do the "take two PTF's and call me in the
morning". But we had followed all of IBM's instructions and if we still
aren't satisfied with the situation (problem still not fixed), we make a
lot of noise to IBM and always demand further escalation.

I know, a good number of folks use this newsgroup exclusive to get
assistance for both hardware and software problems with their AS400's
because they either don't have a support (or software subscription)
contract with IBM and/or running unsupported or out-of-date AS400 systems
(hardware and software). But all I'm suggesting is that if you're already
paying somebody for support, I'd be going there first and getting what I
paid for.

If somebody here (in this NG) already has the answer, that's great.

I'm just suggesting that IBM should have already addressed and fixed this
for you if you have a support contract with them. If not, demand your
money back!

I'm sorry if this note comes off a little strong....

0 new messages