Technical data

To make changes to your OSMCONF file take effect, see “Creating and Using an OSMCONF
File” (page 15).
OSM Upgrade Considerations
To help ensure accurate alarm reporting in OSM, when upgrading to a new OSM servers SPR (or
falling back to a previous version), you should purge the IAREPO file from $SYSTEM.ZSERVICE.
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 configuration changes (see “Optional OSM Configuration”
(page 15) and “OSM Upgrade Considerations” (page 33)), 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
This table lists and describes the OSM persistent processes:
File NameSymbolic NameDescriptionProcess Name
$SYSTEM.SYSnn.CIMOM$ZZKRN.#OSM-CIMOMMain OSM server process
(Common Information Model
Object Manager)
$ZCMOM
$SYSTEM.SYSnn.APPSRVR$ZZKRN.#OSM-APPSRVRApplet Server process –
uploads client files to the
Service Connection
$ZOSM
$SYSTEM.SYSnn.EVTMGR$ZZKRN.#OSM-OEVEvent Viewer Manager
process – server for Event
Viewer requests
$ZOEV
$SYSTEM.SYSnn.ZSPE$ZZKRN.#SP-EVENTSP Event Distributor process
– writes SP events to $ZLOG
$ZSPE
$SYSTEM.SYSnn.EMSACOLL$ZZKRN.#ZLOGEMS Collector for service
events
$ZLOG
$SYSTEM.ZOSMLH.INITRD$ZZKRN.#OSM-CONFLH-RDEMS Routing Distributor –
used by ServerNet Cluster
$ZOLHI
Automatic Line Handler
Configuration to send events
to $ZOLH
$SYSTEM.ZOSM.CTCPIP0
$SYSTEM.ZOSM.CTCPIP1
$ZZKRN.#
ZTCP0$ZZKRN.# ZTCP1
TCP/IP processes – required
by the Service Connection,
$ZTCP0$ZTCP1
Notification Director, and
Event Viewer for HTTP over
TCP/IP communication
$SYSTEM.SYSnn.SNMPTMUX$ZZKRN.#OSM-SNMPTMUXOSM now starts the
SNMPTMUX process as
$ZTMUX
$ZTMUX, a standard
persistent process used by
OSM providers to convert
SNMP traps to EMS events.
Other OSM Server Processes
This section describes the other OSM and OSM-related (*) 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.
OSM Upgrade Considerations 33