Checking the Results of Actions in the DBA Planning Calendar 
Use
This section tells you how to check the results after an action has been executed in the
DBA Planning Calendar. Actions executed in the DBA Planning Calendar generate the following:You can view both of these in the DBA Planning Calendar.

Background jobs are used to schedule actions and these background jobs generate job logs. You can view all the information using the Calendar. In addition, you can view all previous archive and backup actions with the archive and backup Monitor.
Prerequisites
You are ready to use CCMS. Refer to
Getting Started in CCMS with Informix DBA.Procedure
To display the current state of an action (past, current, or previous) in the Calendar, do the following:
The system displays the calendar, with a list of actions for each day. The actions are color-coded, with the following meanings:
Action Color Coding in the DBA Planning Calendar
Color |
Meaning |
Blue |
Action scheduled for execution today |
Green |
Action completed successfully |
Yellow |
Database activity log missing or warning issued |
Red |
Action failed – analyze problem and repeat action if necessary to ensure availability of a complete backup or continued safe operation of the database |
The system displays a list of actions for the day you selected.
The following values are possible:
Action States in the DBA Planning Calendar
Status |
Meaning |
SCHED |
Action is scheduled but the scheduled time has not yet arrived |
OK |
Action was completed successfully |
ERROR |
Action was not completed successfully |
EXEC |
Action is being carried out |
N.A. |
No information available on state (for example, if no action log normally written for the action) |
The statuses ERROR and N.A. are highlighted in red in the Calendar. If there is one ERROR in one day and no OKs, then the header for that day is also highlighted.
The system displays the action log, if there is one. The system does not generate an action log for every type of action.

A job log (see next step) contains general information, whereas an action log contains specific information about the database aspect of the action. You normally check the action log. If there is a problem with the job, you should also check the job log.
Action logs are sometimes assigned to a later action than they should be, due to problems with the timestamp used to assign logs to scheduled actions. In some cases the action is delayed and even postponed until after the next scheduling time.
This occurs, for example, if no batch work process is available. An action log is then assigned to the action that has the same type and the closest corresponding timestamp. Unfortunately this means that the action log is then assigned to the next scheduling time and the log for the originally scheduled time is incorrect.
The system displays the job log.
Result
By checking the results of actions executed in the DBA Planning Calendar, you can make sure that your database is functioning optimally. For example, you can tell if a database backup has failed, fix the problem, and schedule it again immediately. Therefore, you can avoid downtime for your R/3 System.
See also:
Choosing a Predefined Action Pattern in the DBA Planning Calendar Scheduling Actions in the DBA Planning Calendar Background Processing DBA Planning Calendar (Informix)