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

Getting Started With OSM Applications
OSM Migration Guide—527273-015
5-9
Functional Differences
Propagation of Subcomponent Problems
As with TSM, alarms and problem attributes on resources in the OSM Service
Connection are propagated up to parent objects. However, instead of displaying
Subcomponent State attributes (on the Attributes tab) for the parent object, the OSM
Tree pane displays a special icon over parent objects to indicate problems with
subcomponents (as Figure 5-8 illustrates).
Alarm and Attribute Suppression
Another new feature in OSM is the ability to suppress alarms and problem attributes.
You can acknowledge a known problem and keep it from propagating problem
conditions all the way up to the system icon (as Figure 5-9
illustrates).
In this example, you might want to suppress the problem attribute on the tape drive
because it is a known problem and you do not want to miss other problems that arise
on the system. After you suppress the problem attribute (see Figure 5-10
), that
Figure 5-8. Propagation of Subcomponent State Problems
VST020.vsd