OSM Migration and Configuration Guide (G06.30+)

OSM Server-Based Components
OSM Migration and Configuration Guide—527273-021
3-7
Starting OSM Persistent Processes
Starting OSM Persistent Processes
Once you have installed all required server-based OSM and requisite SPRs from the
SUT (using DSM/SCM) and completed any desired configuration changes (see
Optional OSM Configuration on page 3-2), use this TACL command to invoke the OSM
Configuration script and start the OSM persistent processes (other than $ZTCP0 and
$ZTCP1):
RUN $SYSTEM.ZOSM.ADDTOSCF
When you start OSM server processes, OSM disables various TSM functionality in the
TSM configuration file (TSMINI). These changes are desirable, to avoid unnecessary
(redundant) system impact; however the changes to the TSMINI file do not take effect
until you restart TSM. For that reason, you should stop and restart $ZTSM after starting
OSM processes. For more information on these and other TSM coexistence and
fallback issues, see Section 6, TSM Coexistence and Fallback.
This table lists and describes the OSM persistent processes:
Process
Name Description Symbolic Name File Name
$ZCMOM Main OSM server process
(Common Information Model
Object Manager)
$ZZKRN.#OSM-CIMOM $SYSTEM.SYSnn.CIMOM
$ZOSM Applet Server process –
uploads client files to the
Service Connection
$ZZKRN.#OSM-
APPSRVR
$SYSTEM.SYSnn.APPSRVR
$ZOEV Event Viewer Manager
process – server for Event
Viewer requests
$ZZKRN.#OSM-OEV $SYSTEM.SYSnn.EVTMGR
$ZSPE SP Event Distributor process
– writes SP events to $ZLOG
$ZZKRN.#SP-EVENT $SYSTEM.SYSnn.ZSPE
$ZLOG EMS Collector for service
events
$ZZKRN.#ZLOG $SYSTEM.SYSnn.EMSACOLL
$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