OSM Migration Guide (G06.27+)

OSM Server-Based Components

OSM Migration Guide—527273-013

3-3

Creation of System Inventory Files

physical connections are made through dedicated ports on either an E4SA, FESA, or

GESA, or through a Gigabit 4-port ServerNet adapter (G4SA) in an IOAM enclosure.

To configure these optional TCP/IP processes for OSM connectivity, edit the

OSMCONF file to specify TCP/IP processes in addition to 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.

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.

Creation of System Inventory Files

For T0682G06 AAC and later, OSM 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 are attached to the IRs

if 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 or later.

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.