To fill shared memory

You can load parts of the data dictionary into shared memory, such as data definitions, objects, reports, and domains.

To specify which parts must be loaded into the shared memory, use these sessions:

• Shared Memory Data (ttaad4156m000):

  To load program and report objects.

• Package Combinations (ttaad1120s000):

  To load table definitions and domains.

After a conversion to runtime, the data specified in these sessions is stored in the $BSE/lib/srdd_tab6.2 file.

For details on the procedure to fill the shared memory, see Infor Enterprise Server Administration Guide.

The parts of the data dictionary loaded into shared memory have an entry that consists of the inode number, date, time, and name. If the entry of a part in shared memory does not match the entry for that part on hard disk, the parts on hard disk are loaded locally, but not into shared memory. The old part remains in shared memory until you execute shmmanager –k to delete shared memory blocks. You must then use shmmanager –i to reinstall shared memory.

Use the srdd_init program to load the parts of the data dictionary into shared memory. The available options are:

• –l: Print what actions the program has performed, including error messages, if any. Use only in combination with the –i option.
• –i: Initialize the parts that must be loaded in shared memory.
• –p: Print a list of loaded components.
• –v: Version information of the program.

Use the shmmanager –s command or the ipcs –m UNIX command to see which segments are used and how much space is left to load other parts of the data dictionary.

Error messages and other messages are written to stderr. To write these messages to a file, specify this command:

srdd_init –i 2> file name

The ${BSE}/etc directory contains the Rc.start file. This program is executed at system startup. Shared memory is installed, filled, and initialized for a BSE environment specified in this file. The shmmanager, and srdd_init programs are used.