jharris
ADSM.ORG Member
- Joined
- May 24, 2004
- Messages
- 166
- Reaction score
- 0
- Points
- 0
- Location
- Victoria, Australia
- Website
- Visit site
Guys,
We've been running an enterprise TSM environment with 7 or so TSM servers communicating to a TS3500.
A single TSM Library Manager instance was created some time ago and manages all of the mount requests from the other TSM server library clients.
Our TS3500 is ALMS enabled and also has attached a couple of C06 (IBM 3593) controllers for IBM Z10 Mainframe to share the library with seperate dedicated tape drives.
We were speaking with an IBM engineer this week who suggested we should ditch the TSM Library Manager and use the ALMS feature built into the TS3500 for library management. Is anyone doing this and how does this effectively change our environment, keeping in mind our TSM Library Manager has a library definition of type SCSI and the TSM library clients are type SERVER.
Cheers.
We've been running an enterprise TSM environment with 7 or so TSM servers communicating to a TS3500.
A single TSM Library Manager instance was created some time ago and manages all of the mount requests from the other TSM server library clients.
Our TS3500 is ALMS enabled and also has attached a couple of C06 (IBM 3593) controllers for IBM Z10 Mainframe to share the library with seperate dedicated tape drives.
We were speaking with an IBM engineer this week who suggested we should ditch the TSM Library Manager and use the ALMS feature built into the TS3500 for library management. Is anyone doing this and how does this effectively change our environment, keeping in mind our TSM Library Manager has a library definition of type SCSI and the TSM library clients are type SERVER.
Cheers.