Probably not the cause of your problem, however be aware that using a port 
number in the 1024-4999 range means that you are risking clashing with an 
"ephemeral" port number.

IBM's statement about ephemeral port numbers :

"Both server applications and client applications have port numbers. A server 
application uses a specific port number to uniquely identify this server 
application. The port number can be reserved to a particular server, so no 
other process ever uses it. In an IBM TCP/IP Services environment, you can do 
this using the PORT statement in the hlq.PROFILE.TCP/IP configuration data set. 
When the server application initializes, it uses the bind() socket call to 
identify its port number. A client application must know the port number of a 
server application in order to contact it.

Because advance knowledge of the client's port number is not needed, a client 
often leaves it to TCP/IP to assign a free port number when the client issues 
the connect() socket call to connect to a server. Such a port number is called 
an ephemeral port number; this means it is a port number with a short life. The 
selected port number is assigned to the client for the duration of the 
connection, and is then made available to other processes. It is the 
responsibility of the TCP/IP software to ensure that a port number is assigned 
to only one process at a time."

The ephemeral port numbers are in the range 1024-4999. IBM recommend that your 
server applications use port numbers above 5000."

Rob Scott
Developer
Rocket Software
275 Grove Street * Newton, MA 02466-2272 * USA
Tel: +1.617.614.2305 
Email: [email protected] 
Web: www.rocketsoftware.com

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of 
Vince Getgood
Sent: 29 April 2009 14:19
To: [email protected]
Subject: TEPS and TEMS

Hi all,
I'm in the process of trying to install TEPS (Tivoli Enterprise Portal Server) 
on my PC (for testing).

We have two LPARS, each with it's own TEMS (Tivoli Enterprise Management Server 
- Don't ask me why we have two - histerical, er, sorry, historical)

I've configured the TEPS to look for the primary TEMS on one of the LPARS, but 
when I start up the TEPS, I see the following in the logs (IP address 
xx.xx.xx.xx' is the IP address of the LPAR NOT xx.xx.xx.xx'!): -

(49F84CD2.0005-
1504:ctsqlconnectionsql1.cpp,660,"CTSQLEvaluatorSQL1_i::Connection::_init")
SQL1: Looking for hub at 'IP:#xx.xx.xx.xx'...
(49F84CF2.0000-1504:kdcc1sr.c,589,"rpc__sar") Endpoint
unresponsive: "ip:#xx.xx.xx.xx':1918", 1C010001, 32, 5(2), FFFF/2, 1.1.1.6, 
d7121a
(49F84CF5.0000-1504:kdcl0cl.c,129,"KDCL0_ClientLookup")
status=1c020006, "location server unavailable", ncs/KDC1_STC_SERVER_UNAVAILABLE
(49F84CF5.0001-1504:kdsnccns.c,260,"NCSErrorMessage") CT/DS RPC Error: 
DSR040 - lb__lookup_annotation abnormal return
(49F84CF5.0002-1504:kdsnccns.c,59,"ConvertNCSStatus") NCS Status Code: 
1c020006
(49F84CF5.0003-1504:kdsnccns.c,209,"ConvertNCSStatus") CT/DS status
returned: 172
(49F84CF5.0004-
1504:ctsqlconnectionsql1.cpp,715,"CTSQLEvaluatorSQL1_i::Connection::_init")
SQL1: Hub lookup failed. rc: 5

I'm told the port is open on all firewalls, but I'm getting the network guys to 
check.

Port 1918 is not reserved in my TCP/IP stack on z/OS.

Can anybody think of anything I've missed?

TIA.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: GET IBM-MAIN INFO Search the archives at 
http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to