Re: disabling TCPIP commmethod
2001-09-24 02:58:33
Subject: |
Re: disabling TCPIP commmethod |
From: |
Pothula S Paparao <9pothula AT SG.IBM DOT COM> |
Date: |
Mon, 24 Sep 2001 14:55:10 +0800 |
Hi matt.
This sreekumar. Its intresting to see u in this list. i think u might have
red my previous mail answering your query. i never seen ur id while
replying, thought that one of *SMer in the list. THanks for the solution.
regards
sree.
"Matthew A. Bacchi" <mbacchi AT BTV.IBM DOT COM>@VM.MARIST.EDU> on 09/22/2001
02:36:31
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: disabling TCPIP commmethod
OK folks, this one has bothered me for years. I want to disable the TSM
server
completely while I do some work. Rather than using the "disable sessions"
command, I want to in effect disable TCPIP connections altogether. I have
attempted commenting out "COMMmethod TCPIP" in the dsmserv.opt file, but it
appears that this is the default, so it has no affect.
Besides the obvious answer of disconnecting the network cable, how can I
force
the TSM server to ignore every TCPIP request. When sessions are disabled,
the
activity log shows connection started, than a message indicating that user
access is disabled. I want to avoid this.
Thanks in advance.
-Matt
/**
/**
** Matt Bacchi mbacchi AT us.ibm DOT com
** IBM Global Services SDC Northeast
** F6TG; MD Filesystems/Internet (802) 769-4072
** ADSM & AFS/DFS Backup (tie) 446-4072
**/
|
|
|