ADSM-L

Re: Number of Sessions?

2003-11-04 08:49:30
Subject: Re: Number of Sessions?
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 4 Nov 2003 06:45:56 -0700
I don't know for sure, but this may be due to another application using
port 1500. There is an article on the IBM site, http://www.ibm.com, that
discusses this symptom. Don't know if that's your problem, but I thought
I'd mention it. Go to the site and at the top, middle of the page you'll
see a "search" text box. Searching on BPX1COMM should locate the article
for you. Maybe that will shed some light.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




John Naylor <john.naylor AT SCOTTISH-SOUTHERN.CO DOT UK>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11/04/2003 06:22
Please respond to "ADSM: Dist Stor Manager"

        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Number of Sessions?


Any help welcome,
I am currently seeing an intermittant  problem  with my TSM 4.2.2 0S390
server refusing to acceprt any new sessions after seeing these messages

ANR9999D BPX1COMM(1978): ThreadId<20025> BindListenSocket: ANRBND(2)
failed:
rv=-1 rc=1115 rsn1=744C rsn2=7247
ANR5099E Unable to initialize TCP/IP driver - error binding acceptor
socket 55
(rc &eq; 1).

TSM has to be recycled before new sessions can connect.
IBM support has been limited to saying that that there is no existing fix
for our problem amd that tracing the problem further will need an upgrade
to a supported code level.
We will be doing exactly that, but not for a few weeks.
In the meantime I wonder if anyone else has seen similar.
We are not exceeding the maximum scheduled sessions and I have increased
region size,
but the problem is still there. The hit occurs shotly after a  burst of
new
scheduled sessions
connects to the host server.
The maximum number of connected sessions I have seen before a hit is 62
against a
maximum scheduled sessions value of 80% of maxsessions 100
Clients resource utilization is the default 2, so a subsidiary question is
do both client sessions count in the number of scheduled sessions, if not
then the maimum number of scheduled  sessions connected would only be 31.

thanks,
John



**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**********************************************************************

<Prev in Thread] Current Thread [Next in Thread>