OSM Migration Guide (G06.28+)
Table Of Contents
- What’s New in This Manual
- About This Guide
- 1 Introduction to OSM
- 2 Preparing for OSM
- 3 OSM Server-Based Components
- 4 OSM Client-Based Components
- 5 Getting Started With OSM Applications
- 6 TSM Coexistence and Fallback
- A Migrating Your Registry Settings
- B Memory Guidelines for OSM
- C Configuring Remote Services
- Configure Modem for Dial-In and Dial-Out
- Create Windows User Name
- Configure Carbon Copy 5.7 or Microsoft NetMeeting for Dial-In
- Configure OSM Notification Director (ND) for Each Host Server
- Configure OSM Notification Director (ND) for Dial-In and Dial-Out
- Configure Incoming Connections
- Reconfigure System Standby and Hibernate Mode
- D Troubleshooting
- E Uninstalling TSM
- Index
OSM Server-Based Components
OSM Migration Guide—527273-015
3-4
Configuring Automatic Data Collection
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.
Configuring Automatic Data Collection
For T0682G06 AAC and later, OSM has enhanced automatic data collection
capabilities. If enabled, OSM automatically collects diagnostic data whenever a
hardware failure causes a Problem Incident Report (IR) to be created.
Automatic data collection is enabled by an OSM Service Connection system-level
action (Enable/Disable Automation of Data Collection), and is configured through a
combination of OSMCONF file settings and Service Connection actions. You can copy
the following settings from the OSMINI file included with T0682 AAC (or later) into your
existing OSMCONF file. (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.)
ADC-related
OSMCONF Parameters Purpose/Effect
Possible
Values Default
AdcDelayTimeInMin
Delay time (in minutes) between the time
that the initial Problem IR is received and
data collection begins. The purpose is to
conduct a single data collection for all
related Problem IRs.
5 to 60 15
AdcEventTimeinHrs
Time (in hours), prior to when the Problem
IR is generated, that the data collection will
collect EMS events from $ZLOG and $0.
1 to 60 12
EnableNDData
Enables ability to send a Diagnostic Data IR
to the OSM Notification Director. (Not visible
in OSM ND version T0632 AAK; however,
Problem IRs also provide the location of
collected data files in ZZAA alarm details.)
ON/OFF ON
AdcFilColTimeinMin
Specifies the time period (in minutes), after
the initial Problem IR is created, that ZZAA
and ZZPS files will be collected.
5 to 120 5