Eric, Thanks for the info. Did you really mean TSM 5.x.x or did you mean to say AIX 5.x.x?
Chet At 02:23 PM 1/30/2003 +0100, you wrote:
Hi Chet! It looks like IBM dropped support for AFS in TSM 5.x.x. This is probably because of the status of AFS itself: it is now open source an IBM has extended support until (I believe) the end of this year. I have opened an IBM Support, but I haven't had an answer yet. If I do, I will post it here. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -----Original Message----- From: Chet Osborn [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 00:20 To: [EMAIL PROTECTED] Subject: AIX TSM Client and AFS/butc Hi, Two questions: 1) We've recently upgraded our TSM (AIX 4.3.3) server to v5.1.5.4. However, we're running the TSM 3.7.1 client on our AFS fileservers. I'd like to upgrade the client software of the AFS servers to 5.1.5, but can't find any relevant documentation. Anyone aware of any potential problems? 2) The TSM 5.1.5 client README.AFSDFS file states NOTE: The AFS/DFS versions of TSM executable files are only available for AIX. 4.3.X Is this just referring to removal of the dsmafs/dsmcafs client, or is there an AFS/butc problem upgrading to AIX 5.1? Chet Osborn Staff Systems Programmer Rensselaer Polytechnic Institute ********************************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **********************************************************************
