OSM Migration Guide (G06.26+)

OSM Server-Based Components

OSM Migration Guide—527273-010

3-2

Optional OSM Configuration

It is not necessary to create a configuration file to use OSM with the default settings.

However, if you want to alter any default settings or take advantage of the following

OSM features, you must create and use an OSMCONF file:

•

Configuring additional TCP/IP stacks for high-speed Starting OSM Persistent

Processes through ServerNet adapter ports.

•

Adjusting the processor priority rating assigned to OSM processes relative to other

applications. For more information, see “OSM Performance Considerations”

Support Note (S03133A).

•

Disabling creation of Configuring System Inventory Files.

•

Some optional parameters for Configuring Automatic Data Collection.

Creating and Using an OSMCONF File

To create an OSMCONF file from an OSMINI template file and to put your

configuration changes into effect:

1. Go to $SYSTEM.ZSERVICE and copy OSMINI to create a new file named

OSMCONF.

2. Edit the OSMCONF file to customize the default settings as desired. To avoid

possible problems, delete blank lines from the OSMCONF file.

3. When you start OSM server processes, configuration settings are read from the

OSMCONF file if one exists in that location. If not, OSM default settings are used.

To change your settings after OSM is running, select Reload Configuration

Settings from the OSM Service Connection Tools menu. To complete this

operation, you are instructed to restart the $ZOSM and $ZOEV processes.

Configuring Additional Stacks for OSM Connectivity

This configuration option is used as an alternative to the default OSM TCP/IP stacks:

•

When connecting to OSM through a nondedicated operations LAN

•

For faster response between OSM Service Connection and the server

Like any changes to OSM configuration defaults, these changes are easiest to make

before you start OSM processes ($ZOSM and $ZOEV in this case). However, you can

also make the changes to your OSMCONF file take effect after OSM processes have

already been started, as described in Creating and Using an OSMCONF File.

Note. OSMINI is a template file delivered as part of T0682 so that you can create your own

customizable OSMCONF file. Because the OSMCONF file is user-created and not installed by

OSM, when you upgrade to a new T0682 SPR, your customized settings are not overwritten.