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-7
Other OSM Server Processes
Other OSM Server Processes
This section describes the other OSM server processes that are started by the OSM
persistent processes described in the preceding section. For each of these processes,
the process name is dynamically assigned.
$SYSTEM.SYSnn.RALPRVD and $SYSTEM.SYSnn.RALPRVNP
Launched by $ZCMOM, these Resource Access Layer Providers are responsible for:
•
Interacting with SP and subsystems such as Storage, SLSA, etc., to gather
attributes and states for system resources
•
Executing all actions on OSM objects
•
Triggering Incident Analysis to generate and clear alarms
RALPRVD is used for initial discovery, initial incident analysis, event processing and all
action execution that require a super-group user.
RALPRVNP is used for action executions that do not require a super-group
permission.
The maximum number that can run simultaneously is 48:
•
Maximum of eight RALPRVD processes for event processing
•
Maximum of eight RALPRVD processes for refresh or reanalyze action processing
•
Maximum of eight RALPRVD processes for short-term super-group action
processing (Start/Stop disk, etc.)
•
Maximum of eight RALPRVD processes for long-term super-group action
processing (Firmware Update, Validate Checksum, etc.)
•
Maximum of eight RALPRVNP processes for short-term non-super-group action
processing (Responsive Test, etc.)
•
Maximum of eight RALPRVNP processes for long-term non-super-group action
processing (None at this time)
$ZOLHI EMS Routing Distributor –
used by ServerNet Cluster
Automatic Line Handler
Configuration to send events
to $ZOLH
$ZZKRN.#OSM-
CONFLH-RD
$SYSTEM.ZOSMLH.INITRD
$ZTCP0
$ZTCP1
TCP/IP processes – required
by the Service Connection,
Notification Director, and
Event Viewer for HTTP over
TCP/IP communication
$ZZKRN.# ZTCP0
$ZZKRN.# ZTCP1
$SYSTEM.ZOSM.CTCPIP0
$SYSTEM.ZOSM.CTCPIP1
Process
Name Description Symbolic Name File Name