Kernel Requirements

Set the kernel parameters as shown in the following sections. The kernel parameter sizes shown in this section are the changes you need to make to use Lawson applications. You must also add these Lawson Software requirements to those of your third-party vendors. For example, if your third-party vendor requires you to set the SEMMNS parameter to 80 and Lawson requires you to add an additional 100, you would add the two requirements and set the parameter to 180.

It is important that you understand these kernel parameters before you change them. Make sure they do not conflict with other system parameters. If you need help with implementing these kernel changes, see the user manual for your UNIX system or consult your UNIX system manufacturer.

maxfsiz (ULIMIT)

The maxfsiz parameter does not apply to the HP/9000 operating system.

The maxfsiz parameter reflects the maximum size of a physical file that you can create or expand on your disk. You must know your anticipated user file (print files, work files, database reorganization files, and others) sizes to set this parameter correctly. You also must know the largest file size you can expect on your machine. Although it is critical to have the parameter set up correctly for your current file size requirements, you can adjust this parameter at a later date if your requirements change.

On some UNIX-based operating systems, the ULIMIT parameter is separate from, and in addition to, the MAXFSIZ kernel parameter. ULIMIT works similarly to the MAXFSIZ parameter and is set in addition to, and not in place of, the MAXFSIZ kernel parameter.

This example illustrates how and where the additional ULIMIT parameter can reside. For complete information, see the system administration manual for your UNIX system.

In the file named /etc/default/login, add or update the following parameter. (You must log in as root.)

ULIMIT= 40960(ULIMIT)

This example reflects the minimum (default) size for ULIMIT of 40,960 512-byte blocks, or 20MB. You should adjust this value for the needs of your site. Your site will probably require a larger number, but you should not assign a value lower than the suggested size.

If you are using the Oracle database, the ULIMIT parameter does not control database file-size limits, although it does control database-reorganization file sizes.

msgmax (MSGMAX)

The msgmax parameter defines the maximum size of a message. Lawson requires a minimum default size of 8192 for this parameter.

Note: For Solaris 10, this parameter is obsolete.

msgmnb (MSGMNB)

The msgmnb parameter defines the maximum size of a message queue. Lawson requires a minimum default size of 16384 for this parameter.

Note: For Solaris 10, this parameter has been replaced by process.max-msgqbytes

msgmni (MSGMNI)

The msgmni parameter defines the maximum number of message queues. The recommended value is based on the parameters in the database driver configuration file (ladb.cfg):

(FILES/LFILES) + FOREIGN + USERS + 25

The USERS parameter sets the maximum number of CPU processes, approximately four for each concurrent login, allowed to access Lawson. See the appropriate Lawson manual for the relational database you use.

Note: For Solaris 10, this parameter has been replaced by project.max-msg-ids

semmns (SEMMNS), semmnu (SEMMNU), or semmsl (SEMMSL)

SEMMNS defines the number of semaphores system-wide.

SEMMNU defines the number of undo structures system-wide.

SEMMSL defines the number of semaphores in a set.

Note: If you are performing a fresh Lawson System Foundation install, you must determine the value of USERS in ladb.cfg file before can adjust the value of SEMMSL. The value of SEMMSL should be equal or greater than the value of USERS indicated in ladb.cfg file.
Note: For Solaris 10, the semmns and semmnu parameters are obsolete. The semmsl parameter has been replaced by process.max-sem-nsems.

The USERS parameter in the database server configuration file (ladb.cfg) sets the maximum number of CPU processes, approximately four for each concurrent login, allowed to access Lawson. See the appropriate Lawson manual for the relational database you use.

To increase the USERS parameter or to increase the number of engines (ladb, Oracle) being used, you must also reset these kernel parameters using the following guidelines.

SEMMNS = USERS * (Number of database engines or servers) + 25

This includes: one for Lawson Environment one for each relational database engine, server, Oracle_SID, or DB2_instance

For example, if you use Lawson with Oracle and have one Oracle_SID, the number of engines or servers is 2, one for Lawson Environment, and one for the Oracle_SID. You would add one for each additional SID.

SEMMNU = SEMMNS SEMMSL = SEMMNS

For more information about the ladb.cfg file, see the Lawson Administration: Server Setup and Maintenance guide.

shmmax (SHMMAX)

The shmmax parameter defines the maximum size of a shared memory segment. The recommended value is:

SHMMAX = USERS * 10,000

Note: For Solaris 10, this parameter has been replaced by project.max-shm-memory

shmmin (SHMMIN)

Note: This parameter applies only to the Sun Solaris operating system. For Solaris 10, this parameter is obsolete.

The shmmin parameter defines the minimum size of a shared memory segment. For the Sun Solaris 9 operating system, both the shmmax and shmmin parameters must be set.

maxuproc or maxuprc

The maxuproc or maxuprc parameter defines the maximum number of processes for a user. At a minimum, set this parameter to 160. Larger sites might need to use a higher number.

maxfiles

The maxfiles parameter defines the number of files a process can use. You might need to adjust this parameter depending on your requirements.

msgtql

This parameter specifies the maximum number of messages in all queues managed by the Lawson services. Infor recommends 256 as a starting point.

Note: For Solaris 10, this parameter has been replaced by process.max-msg-messages.

nproc

The nproc parameter defines the maximum number of processes system-wide. You might need to adjust this parameter, depending on your requirements.

nfiles

The nfiles parameter defines the maximum number of files open at one time system-wide. This parameter is used on HP systems. The error message "File table overflow" indicates that nfiles is set too low. The parameter ninodes is tied to nfiles. Typically, when an adjustment is made to nfiles, ninodes must also be adjusted.