Have you put a 5 or 7 or 9 (don?t remember the option) against the 5704 and
see the device under there? I bet you will see TAP0x.

Pete

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rick baird
Sent: Wednesday, March 18, 2009 8:55 PM
To: Midrange Systems Technical Discussion
Subject: Re: Tape hardware resources

Kirk,

I believe the problem is with the hardware resource.  I did WRKHDWRSC
*STG and it lists:

Resource        Type-model  Status                Text
CMB01            2844-001   Operational           Combined function IOP
  DC01           2757-001   Operational           Storage Controller
  DC03           5704-001   Operational           Tape Controller
  TAPMLB03       3582-001   Operational           Tape Library

TAPMLB03 is not the old tape library name, the device is not a
3582-001, it's a 3580-002.

#1 Looks like you might need a PTF id a single cart ( non-autoloader )
reports in as Tape Library ( autoloader ).

Not sure what you mean here, the tape drive is an autoloader tape library.

#2 The key here is 'non-reporting'..right now it is reporting. I think
you'll have to IPL with the drive OFF to get it non-reporting

well that blows chunks. hopefully it won't come down to that.

#3 Also If there is room, I'd move the 5704 off the same IOP as any disk
controller. backups should run much faster

baby steps... I just want a current backup at this point. ;-)

more info- the TAPMLB03 is a name that didn't exist before this came
up. the old name was TAPMLB02.

I think I'm going to have them call IBM service. I'm working remotely
and the tape and system are in an offsite secure facility that will
burn a couple hours for someone just to get in the same room with it.

Thanks for the help though!

Rick

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2026 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.