Event Management Best Practices › Startup Procedures

Startup Procedures

The CAIPROC member NSMEMSTR is used to start Event Management. By default, this starts processes caiopr, stardaemon, ca_calendar, newdaylog, and caidoc.

Note the following startup considerations:

• All processes must be started with UID(0), and CAICCI must be active before they are started. To ensure that CAICCI is completely initialized, you can start Event Management as part of the CAIENF autocmds.
• The stardaemon does not require any additional services.
• The caiopr daemon has the option of using the repository. If the definition of message actions and calendars, or both, are desired, the repository is needed, and must be started prior to Event Management. You must ensure that the STEPLIB environment variable, in the PROFILE file, is set correctly prior to starting caiopr.
• If you are using CA OPS/MVS to handle the processing of messages, the repository is not required. The startup of caiopr will receive some warning messages concerning the connection to the repository and that the messages cannot be reloaded, but caiopr will continue processing normally and the messages can be ignored.
• The user ID assigned to Event Management must be UID(0). This is required to be able to switch a user from the Event Management user ID to the user ID of the client signed on. This prevents the client from being able to issue commands they would normally not be allowed to enter for the Unicenter console.
• If the SNMP trap listener, catrapd, needs to be started, you must locate the following line in the /cai/nsmem/opr/scripts/emstart file and remove the pound sign (#) from the beginning of the line:

  #unicntrl start snmp
  

  When finished, the line should appear as follows:

   unicntrl start snmp