Configuring the initialization file

Whether using the single process CompoundSystem or separate Launcher processes comprising one or more .msl system files, you can configure the Launcher initialization file. You can rename it (the default name is config.yaml) as well as make modifications to its contents.

Some of the changes you can make to the initialization file include modifications to the following resource manager settings in the [Resource Manager] section:

Resource Management Settings: Description
CentralMgmt: Valid values are:
0, local resource management
1, global (centralized) resource management
Default is 0.
TableSize: Size in megabytes for the Resource Manager table.
Default is 10.

If the Launcher Administration is set to run systems in separate Launcher processes and the resource manager setting for a Launcher process is set to Local, the CentralMgmt entry in the initialization file has precedence over those other settings. Setting CentralMgmt to 1 will enable global (centralized) resource management. The default is 0 or local resource management.

The TableSize entry is used for both local and global resource management. It determines the initial size of the Resource Manager table before having to re-size it if required. Re-sizing requires all Launchers using the table to re-calculate the entries and might fail if memory cannot be obtained. The value is in megabytes, and the minimum value is 1. The default table size is 10 (10 megabytes).

The following table correlates the size of the Resource Manager table to the number of entries that the table can hold.

Resource Manager Table Size (in megabytes)	Total Entries	Unique Entries (138 bytes average size)
1	5461	4369
5	27306	21845
10	54613	43690
25	136533	109226

Note: There is, at most, one entry for each initialize pending map and one entry for each card for each resource pending map during Launcher processing, depending on the type of resource (file, database, ftp, and so on) and whether it needs WebSphere® Transformation Extender resource management.

When using global resource management, the initial Launcher process that creates the Resource Manager table determines the size for subsequent processes that use global resource management.