IDS Forum

Re:Error 25588 : IDS 7.31UD1 on Solaris8

Posted By: ART KAGEL, BLOOMBERG/ 731 LEXIN
Date: Wednesday, 5 September 2007, at 3:53 p.m.

In Response To: Re:Error 25588 : IDS 7.31UD1 on Solaris8 (Manoj Mohan)

I disagree with this statement Manoj:

> For best performance, specify NET if you require more than one poll
> thread. If you are running Windows, specify NET in all cases.

That used to be the advice and I've always disagreed with it. A couple of
years ago I finally got the IDS folk to look at my recommendations versus
theirs and to test them out. The results were that the docs were change to
match fairly closely to my own recommendations. Those being:

Shared memory connections ONLY in CPU VPs and the number of poll threads must
be equal to the number of CPU VPs for best responsiveness if you will be
actively using the shared memory connections for more than occassional
maintenance connections. TCP connections ONLY in NET VPs and there should only
be a few of those configured sufficient to limit the number of connections
managed by a single poll thread to fewer than 200 which IBM considers to be
efficient. For a full explanation of why I make these recommendations, see the
entry on NETTYPE in the IDS FAQ.

Art S. Kagel

----- Original Message -----
From: Manoj Mohan <ids@iiug.org>
To: ids@iiug.org
At: 9/05 14:19:22

This extract from the manual might make things bit more clear for you..=
..

Basically that number is no. of connections per poll thread....

NETTYPE connection_type,poll_threads,c_per_t,vp_class
connection_type,

identifies the protocol-interface combination to which the poll

threads are assigned. You typically set this field to match the

connection_type field of a dbservername entry that is in the sqlh=
osts

file or registry.
poll_threads

is the number of poll threads assigned to the connection type. Se=
t

this value to no more than NUMCPUVPS for any connection type.
c_per_t

is the number of connections per poll thread. Use the following f=
orm

ula to calculate this number:

c_per_t =3D connections / poll_threads

connections

is the maximum number of connections that you expect the

indicated connection type to support. For shared-memory

connections (ipcshm), double the number of connections for =
best

performance.
vp_class

is the class of virtual processor that can run the poll threads.

Specify CPU if you have a single poll thread that runs on a CPU V=
P.

For best performance, specify NET if you require more than one po=
ll

thread. If you are running Windows, specify NET in all cases. The=

default value for this field depends on the following conditions:=

If the connection type is associated with the dbservername =
that

is listed in the DBSERVERNAME parameter, and no previous

NETTYPE parameter specifies CPU explicitly, the default VP

class is CPU. If the CPU class is already taken, the defaul=
t is

NET.

If the connection type is associated with a dbservername th=
at

the DBSERVERALIASES parameter specifies, the default VP cla=
ss

is NET.

=

"KURT VAN GOMPEL" =

<kvangompel@caami =

-hziv.fgov.be> =
To

Sent by: ids@iiug.org =

ids-bounces@iiug. =
cc

org =

Subj=
ect

Re:Error 25588 : IDS 7.31UD1 on =

09/05/2007 01:10 Solaris8 [9906] =

PM =

=

=

Please respond to =

ids@iiug.org =

=

=

Thank you Art for your quick response.

First of all sorry for dropping the threat in the second message I post=
ed!

I thought the number specified in the parameter NETTYPE was the maximum=
of
concurrent connections of that type. We are having the problem after 50=

sequential connections!
Do I misunderstand the functioning of NETTYPE?
I read somewhere that it is not necessary to specify the number of
concurrent
users for a shared memory connection in the config-file, is that true?

Kurt.

***********************************************************************=
********

Forum Note: Use "Reply" to post a response in the discussion forum.

=

*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.

Messages In This Thread

• Error 25588 : IDS 7.31UD1 on Solaris8
  KURT VAN GOMPEL -- Wednesday, 5 September 2007, at 10:13 a.m.
  • Re: Error 25588 : IDS 7.31UD1 on Solaris8
    Manoj Mohan -- Wednesday, 5 September 2007, at 11:06 a.m.
  • Re: Error 25588 : IDS 7.31UD1 on Solaris8
    KURT VAN GOMPEL -- Wednesday, 5 September 2007, at 11:06 a.m.
    • Re: Error 25588 : IDS 7.31UD1 on Solaris8
      ART KAGEL, BLOOMBERG/ 731 LEXIN -- Wednesday, 5 September 2007, at 11:11 a.m.
  • Re:Error 25588 : IDS 7.31UD1 on Solaris8
    ART KAGEL, BLOOMBERG/ 731 LEXIN -- Wednesday, 5 September 2007, at 11:30 a.m.
    • Re:Error 25588 : IDS 7.31UD1 on Solaris8
      KURT VAN GOMPEL -- Wednesday, 5 September 2007, at 2:10 p.m.
      • Re:Error 25588 : IDS 7.31UD1 on Solaris8
        Manoj Mohan -- Wednesday, 5 September 2007, at 2:18 p.m.
        • Re:Error 25588 : IDS 7.31UD1 on Solaris8
          ART KAGEL, BLOOMBERG/ 731 LEXIN -- Wednesday, 5 September 2007, at 3:53 p.m.
          • Re:Error 25588 : IDS 7.31UD1 on Solaris8
            Manoj Mohan -- Wednesday, 5 September 2007, at 5:36 p.m.
      • RE: Error 25588 : IDS 7.31UD1 on Solaris8
        Clifton Bean -- Wednesday, 5 September 2007, at 2:23 p.m.
      • Re:Error 25588 : IDS 7.31UD1 on Solaris8
        ART KAGEL, BLOOMBERG/ 731 LEXIN -- Wednesday, 5 September 2007, at 3:14 p.m.
        • Re:Error 25588 : IDS 7.31UD1 on Solaris8
          KURT VAN GOMPEL -- Thursday, 6 September 2007, at 4:12 a.m.
          • Re:Error 25588 : IDS 7.31UD1 on Solaris8
            ART KAGEL, BLOOMBERG/ 731 LEXIN -- Thursday, 6 September 2007, at 9:18 a.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.