The Notes_SHARED_DPOOL is a UNIX environment variable. It should be set in the Notes Server UNIX account's .profile, .kshrc, or .cshrc
depending on the shell that is being run.

Notes_SHARED_DPOOLSIZE controls the shared memory segment size that the Notes Server will request from the UNIX kernel. By default,
the Notes Server makes shared memory allocation requests to the kernel at a given size based on the specific UNIX platform. The effect of not
setting the variable may be the error "...insufficient memory...".

Below is a working example of how to set the variable to 16 megabytes.

For c-shell in the .cshrc add:

setenv Notes_SHARED_DPOOLSIZE 16777216

For bourne or korn shell add in the .profile or .kshrc, respectively:

Notes_SHARED_DPOOLSIZE= 16777216
export Notes_SHARED_DPOOLSIZE

NOTE: Read the Supporting Information section for further considerations in regards to your operating system. Information in the Notes Release
Notes on this variable should be disregarded prior to Release 4.1.3 and 4.5, as the settings found there are inaccurate.

Supporting Information:

In general, if a customer sets the variable Notes_SHARED_DPOOLSIZE, it must be greater than the default Notes Server request for allocation
to the operating system. The default allocation by Notes and OS platform are shown in the table below.

Platform OS Notes Ver Default
AIX 4.1.3, 4.1.4 4.1a-4.11a,4.5(a) 8000000 *
AIX 4.1.3, 4.1.4,4.2 4.12, 4.13... 4.51 (RAM IN BYTES /7/2)
HP/UX 10.01 4.1x, 4.5 12000000
Solaris Sparc 2.4, 2.5,2.51, 4.1x, 4.5 1000000
Solaris X86 2.5 4.1x. 4.5 1000000

Before giving more directed guidelines per platform, getting the pertinent information from the ipc table is necessary.

The command "ipcs -mb" (without the quotes) will best show shared memory segments and their allocated size. On all Notes UNIX platforms, the
first segment that the Notes Server allocates is slightly less than one megagbyte. Regardless of the UNIX account name running the Notes
Server (Shown in the OWNER field), the segments that the Notes server or client has allocated begin with 0xf8 in the KEY field of the output.
An example output follows:


IPC status from <running system> as of Thu Dec 5 15:43:01 1996
T ID KEY MODE OWNER GROUP SEGSZ
Shared Memory:
m 8704 0xf8000000 --rw-rw---- admqrk notes 904016
m 8705 0xf8000001 --rw-rw---- admqrk notes 38347922
m 8706 0xf8000002 --rw-rw---- admqrk notes 38347922


AIX customers must watch segment allocation on the operating system for the Notes Server Account. There are only ten memory segments that
an application can allocate through AIX version 4.2. If the customer is routinely allocating eight or nine segments for the Notes Server, increasing
the Notes_SHARED_DPOOLSIZE would be desirable so it does not run out of segments.

* In Notes versions 4.12/4.51 and higher after issuing ipcs -mb you can determine the exact allocation for shared memory segments.

Solaris Sparc and Intel customers running above 100 concurrent users should note that it is practical to move to a 16 megabyte
Notes_SHARED_DPOOLSIZE. This will effectively use the boundaries defined in an intimate shared memory allocation. With an allocation of
16 megabytes, there is no danger of running out of shared memory segments on the Solaris Operating System.


For HP customers, servers run optimally with a maximum of 3 memory segments, inclusive of the small segment. More than 3 segments could
possibly cause performance degradation.

For organizations running 200+ concurrent users: The Notes_SHARED_DPOOLSIZE would be estimated at about 40 megabytes, or higher.

01. preferences	02. Cache	03. Client_Clock	04. adminp_enable_cascade_design_elements
05. tcp_enableipv6	06. debug(all)	07. logstatusbar	08. enforce_policy_bookmarks
09. converter_log_level	10. Log_Connections

04/09/2006 Notes. Updates and DRCC news

06/07/2005 no.Spam.java - Bonded Sender support

05/10/2005 dcShield - free Spam control for Domino

05/10/2005 no.Spam.java - Greylisting now available

05/09/2005 no.Spam.java - New Features

03/30/2005 dcShield - free spam control for Domino

02/17/2005 no.Spam.java - What's New - Challenge/Respons..

02/02/2005 no.Spam.java - New features