Previous Topic: Contact CA TechnologiesNext Topic: actnode.prf-Maintain Message Action Restriction Rules


Event Management Commands

ca_calendar-Start the Calendar Daemon

Applies to UNIX/Linux and Windows

The ca_calendar command starts the Enterprise Management calendar daemon. Normally the calendar daemon is executed as part of startup processing.

Enterprise Management functions such as Job Management Option and Security Management use the calendar daemon to verify a date and time against a specified calendar. You can define calendars through the Enterprise Management command line or GUI interfaces. When started, the calendar daemon loads all calendars that are defined in the Enterprise Management database into the active calendar list. You can modify the active calendar list with the caladmin command.

Syntax

ca_calendar [-f]

Startup Configuration

Execute the Enterprise Management Calendar daemon

Follow these steps:

  1. Verify that the Enterprise Management startup script, $CAIGLBL0000/scripts/rc, was properly integrated in your startup procedure.
  2. Verify that the $CAIGLBL0000/scripts/rc file includes the following statement:
    $CAIGLBL0000/cal/scripts/envset
    

Performance Considerations

To minimize resource consumption, delete calendars from the active calendar list that are not in use.

The calendar daemon is automatically updated only when calendars are defined or altered through the GUI. Add calendars defined or altered with the command-line interface to the active calendar list using the caladmin command with the -a or -u option.

External Influences

CAIGLBL0000

CAICAL0000

CAICAL0001

CAICAL0002

CAICAL0003

Files

$CAIGLBL0000/cal/config/nodename/CA_CalDmon_Lock

Locking file that prevents more than one copy of the calendar daemon from executing concurrently. The locking file contains the process ID of the running calendar daemon. You can change it with the environment variable $CAICAL0003.

Warnings

If the calendar daemon encounters any environmental errors, it automatically shuts down. Other errors, such as missing or incomplete calendars, result in a calendar validation failure. The calendar validation failure causes all calendar analysis requests that name the affected calendar to return an invalid calendar status.

Check the SYSLOG file for any errors the calendar daemon encountered.

Examples

Start the calendar daemon if it is not started:

ca_calendar

Shut down the currently executing calendar daemon to force a new calendar daemon to start, if necessary.

ca_calendar -f

caevtsec-Update Message Action Restriction Rules

Valid on UNIX/Linux

caevtsec is a menu-driven executable that lets you update the rules for sending the message actions COMMAND, UNIXCMD, and UNIXSH to your local host. This executable alters the actnode.prf file with the information you supply. caevtsec is an alternative to using vi or another UNIX/Linux editor to update the file.