OSM Migration Guide (G06.26+)

OSM Server-Based Components

OSM Migration Guide—527273-010

3-3

Configuring System Inventory Files

The default configuration is for the OSM Service Connection to communicate to the

OSM CIMOM (server) process through the service processors (SPs), using $ZTCP0

and $ZTCP1 TCP/IP stacks. (This is the same configuration used when configuring

TSM through a dedicated service LAN.)

To increase OSM performance, you can choose to connect to the server through

dedicated ports on an E4SA, FESA, or GESA CRU. Edit the OSMCONF file to specify

TCP/IP stacks other than the default SP stacks ($ZTCP0 and $ZTCP1):

stack = <TCPIP process name>

For example:

stack = $ZTC00

stack = $ZTC01

If you choose this alternative connection option, use the IP address or host name

corresponding to one of the stacks specified when Establishing an OSM Service

Connection Session or OSM Event Viewer session.

Configuring System Inventory Files

OSM version T0682 AAC has automatic system inventory file creation enabled by

default (you no longer need to perform the Reload Configuration Settings action every

time you want to create a system inventory file). These system inventory files are

created along with Periodic Incident Reports (IRs) and attached to them, provided the

“Suppress Attachment files on Periodic IRs” option is deselected in the OSM

Notification Director Preferences dialog box.

To disable automatic creation of system inventory files, you must set the following

OSMCONF flag to “OFF:”

== INVENTORY_STATE = ON

The ”== ENABLE_INVENTORY = ON” parameter used to configure system inventory

files in earlier OSM releases no longer has any effect and should be removed from

your OSMCONF file. The current ”== INVENTORY_STATE = ON” parameter can be

copied to an existing OSMCONF from the OSMINI template provided with T0682 AAC.

To create an OSMCONF file from the OSMINI, or to put OSM configuration file

changes into effect when OSM processes are already running, see Creating and Using

an OSMCONF File.

For information on initiating Periodic incident reports and viewing attachment files, see

the OSM Notification Director online help.

Note. A system inventory file will not be created if a Periodic IR is generated before OSM

completes system discovery.