OSM Migration Guide (G06.25+)

OSM Server-Based Components

OSM Migration Guide—527273-008

3-3

Enabling System Inventory Files

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.

Enabling System Inventory Files

To enable creation of system inventory files, add (you can copy from the current

OSMINI template) the following syntax to your OSMCONF file (text in green is optional

descriptive text; black text is the actual syntax that must be entered as shown):

== Default value for Inventory feature is OFF. Set ON to

== enable and OFF to disable.

== ENABLE_INVENTORY = ON

For this and other OSMCONF changes to be put into effect when OSM processes are

already running, see Creating and Using an OSMCONF File.

Once this feature is enabled, system inventory files are created the first time a

Periodic incident report is generated. To create system inventory files a again, you

must repeat the Reload Configuration Settings action. To allow attachment of the

inventory files to Periodic incident reports, you must deselect “Suppress Attachment

Files on Periodic IRs” in OSM Notification Director Preferences. For information on

initiating Periodic incident reports and viewing attachment files, see the OSM

Notification Director online help.

Enabling Automatic Data Collection

For G06.25, automatic data collection is no longer enabled in the OSMCONF file.

Check the T0682 softdoc for the current status of automatic data collection. When

available, it will be enabled through system-level actions in the OSM Service

Connection. Only one related parameter will remain in the OSMCONF file, that which

determines how long files are retained on the system before being deleted. The text in

green is optional descriptive text; the black text is the actual syntax that must be

entered as shown (or copied from the current OSMINI template):

== If ADC feature is enabled, specify the number of days for

== which the PAK file is retained. Possible range is 1 to 30.

== ADC_PAK_RETAINDAYS = nn