OSM Migration and Configuration Guide (G06.30+)

Introduction and Check List
OSM Migration and Configuration Guide—527273-021
1-9
Get Acquainted with OSM Applications
OSM Guided Procedures
See OSM Guided Procedures for a comparison to TSM guided procedures.
Try launching a procedure a replacing a CRU in your system (just re-insert the same
CRU back in as the “replacement” CRU, if you have no CRU in need of replacement.
Note the OSM feature to Suppress Problem Incident Report Creation, to suppress
unwanted dial-outs during service procedures (it will be called for if it applies).
OSM Low-Level Link
The OSM Low-Level Link is very similar to the TSM Low-Level Link; in fact, it has
replaced the TSM Low-Level Link as of TSM 2005A client. See OSM Low-Level Link to
learn more.
Launch the OSM Low-Level Link and log on to your system. If you migrated your TSM
system list, the name of your system should appear in the Log On dialog box. If not,
edit your system list to add it, as done in TSM. After logging on OSM Low-Level Link
(assuming your system is already running):
•
Click System Discovery to discover your system.
•
Click Processor Status to monitor or perform actions on processors (after system
discovery, select Processor Status from the Summary menu to access.
The OSM Low-Level Link is used to start your system or load processors just like did
with the TSM Low-Level Link. For more information on using the OSM Low-Level Link,
see the online help available within the application.
OSM Notification Director
The OSM Notification Director is very similar to the TSM Notification Director. See
OSM Notification Director for a comparison and explanation of some key differences.
Try viewing a problem incident report. Create a periodic incident report. Confirm that
dial-outs are working.
OSM Event Viewer
The OSM Event Viewer does look quite different than the TSM Event. See OSM Event
Viewer to learn more about its capabilities and see the online help for information on
how to use it.
Launch it directly, or from within the OSM Service Connection, and try to:
•
Retrieve events based on the criteria you specify.
•
Save your selection criteria by creating an Internet Explorer favorite.
•
Expand individual event to get details, such as cause, effect, recovery information.
•
Save your retrieved event stream.