Re: TSM Windows Client 4.1.2 and MSCS Cluster
Thanks for all your replies. I'm pleased to hear it is working in some places out there on MSCS clusters. For info, I'm running TSM Server v3.7.4.0 on NT Server. My client option file for the shared disks specifies the clusternode option as: clusternode yes I'd be interested in anybody's thoughts. Thanks again Neil The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office 2 The Embankment Sovereign Street Leeds LS1 4BG Registered in England and Wales No 2366682
TSM Windows Client 4.1.2 and MSCS Cluster
Has anybody successfully got the v4.1.2 Windows client working with an MSCS cluster? When I upgraded the TSM client software on one of our clusters, the Scheduler services installed with the DSMCUTIL INSTALL /CLUSTERNODE:YES command no longer start. The problem seems to be to do with the parsing of the ClusterNode value in the Parameters sub-key in the registry. Everytime MSCS attempts to start the Scheduler services for the shared disks, I get the following message in DSMERROR.LOG: 01/06/2001 12:35:37 ANS1107E Invalid option/value: '-ClusterNode='Yes'' The schedulers for the non-shared disks start fine. Do I have to modify the configuration of the Scheduler services for the shared disks somehow? The problem is similar to APAR IC25014, but that was fixed over a year ago. In the end, I installed 4.1.1.16 and that works fine. Neil Schofield The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office 2 The Embankment Sovereign Street Leeds LS1 4BG Registered in England and Wales No 2366682
Re: TSM Windows Client 4.1.2 and MSCS Cluster
I just upgraded by cluster servers (15 of them) from 3.7 client to 4.1.2 clients and they worked fine. No problem with scheduler resource service or backups running. Is your options file set up as "Clusternode=YES" or "Clusternode YES" (should be the second one) -Original Message- From: Neil Schofield [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 07, 2001 8:22 AM To: [EMAIL PROTECTED] Subject: TSM Windows Client 4.1.2 and MSCS Cluster Has anybody successfully got the v4.1.2 Windows client working with an MSCS cluster? When I upgraded the TSM client software on one of our clusters, the Scheduler services installed with the DSMCUTIL INSTALL /CLUSTERNODE:YES command no longer start. The problem seems to be to do with the parsing of the ClusterNode value in the Parameters sub-key in the registry. Everytime MSCS attempts to start the Scheduler services for the shared disks, I get the following message in DSMERROR.LOG: 01/06/2001 12:35:37 ANS1107E Invalid option/value: '-ClusterNode='Yes'' The schedulers for the non-shared disks start fine. Do I have to modify the configuration of the Scheduler services for the shared disks somehow? The problem is similar to APAR IC25014, but that was fixed over a year ago. In the end, I installed 4.1.1.16 and that works fine. Neil Schofield The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office 2 The Embankment Sovereign Street Leeds LS1 4BG Registered in England and Wales No 2366682
Re: TSM Windows Client 4.1.2 and MSCS Cluster
Neil, What version of the TSM server are you running and on what operating system? I encountered the exact same problem and opened up a record with TSM support. I was told that the issue was related to the fact that we were running V3.7.1.0 of the OS/390 TSM server and we needed to be at 3.7.3.0 at a minimum. Are you running a later version of the TSM server than 3.7.1.0? We are planning to upgrade our TSM server very soon and was going to try and install the service again after we upgraded. Jeff Connor Niagara Mohawk Power Corp Neil Schofield [EMAIL PROTECTED]@VM.MARIST.EDU on 01/07/2001 11:21:56 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: TSM Windows Client 4.1.2 and MSCS Cluster Has anybody successfully got the v4.1.2 Windows client working with an MSCS cluster? When I upgraded the TSM client software on one of our clusters, the Scheduler services installed with the DSMCUTIL INSTALL /CLUSTERNODE:YES command no longer start. The problem seems to be to do with the parsing of the ClusterNode value in the Parameters sub-key in the registry. Everytime MSCS attempts to start the Scheduler services for the shared disks, I get the following message in DSMERROR.LOG: 01/06/2001 12:35:37 ANS1107E Invalid option/value: '-ClusterNode='Yes'' The schedulers for the non-shared disks start fine. Do I have to modify the configuration of the Scheduler services for the shared disks somehow? The problem is similar to APAR IC25014, but that was fixed over a year ago. In the end, I installed 4.1.1.16 and that works fine. Neil Schofield The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office 2 The Embankment Sovereign Street Leeds LS1 4BG Registered in England and Wales No 2366682
