Re: Choosing a TCPPort number.

2006-07-12 Thread Maurizio Teruzzi
, 2006 11:49 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Choosing a TCPPort number. We use 1501 and have no problems. If you are not using the TCPCLIENTPORT, I wouldn't think that it would cause troubles, but I'm no expert. But from client side, if you want to go to the first instance, 15

Re: Choosing a TCPPort number.

2006-07-12 Thread Mcnutt, Larry E.
Subject: Re: Choosing a TCPPort number. We use 1501 and have no problems. If you are not using the TCPCLIENTPORT, I wouldn't think that it would cause troubles, but I'm no expert. But from client side, if you want to go to the first instance, 1500, or the second, 1501. That is what we'

Re: Choosing a TCPPort number.

2006-07-12 Thread Bell, Charles (Chip)
But it needs to be hard-coded on both sides. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mcnutt, Larry E. Sent: Wednesday, July 12, 2006 9:37 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Choosing a TCPPort number. TSM 5.3.3.0 AIX 5.3 ML4 I n

Choosing a TCPPort number.

2006-07-12 Thread Mcnutt, Larry E.
TSM 5.3.3.0 AIX 5.3 ML4 I need to choose a TCPPort number for a second TSM instance. Initially I was thinking of using 1501, but then I discovered that 1501 is the default for the TCPCLIENTPORT. But the documentation says that if port 1501 is busy, the scheduler will use another available port.