Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CCM-MON (Application Component) Monitoring⤷
SMOI (Package) CCMS: Monitoring Architecture
Basic Data
| Data Element | ALCONTSTAT |
| Short Description | Alert: Status of Context (active/inactive/....) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Alcontstat |
| Medium | 15 | Context status |
| Long | 20 | Context status |
| Heading | 0 |
Documentation
Definition
The status of a shared memory segment used by the alert monitor.
Possible statuses are as follows:
- Online: Situation normal. The alert monitor is able to gather information from a segment that has this status.
- Communication error: The SAP instance or external program or component is apparently active. The message server lists the instance or program as active. However, RFC calls to the instance or program failed. No data is available from the instance or component that uses this shared memory segment.
You can test the connection to the segment with Transaction SM59. Communication error
- ShutdownShutdown : The SAP instance or external program or component is apparently inactive. The message server has no information on the instance or external program. No communication could be established with the instance or external program, and no data from the instance or program is displayed in the alert monitor.
- Offline: The segment has been manually de-activated. The alert monitor does not try to collect information from this segment until the status is again set to online.
Set a segment offline if you know that an SAP instance or external program is going to be down. The alert monitor will then not register problems with the segment. Remember to set the segment to online again when the instance or external program is re-started.
Background information: In each SAP instance or external component, the alert monitor uses a shared memory segment to hold monitoring data. Such shared memory segments are therefore usually associated with an SAP instance or an external program or system that has been included in the alert monitor.
The shared memory segments are also the source for the information that is displayed in the alert monitor (Transaction RZ20). The alert monitor picks up data from each of the segments known to it. If it cannot reach a segment for some reason, then the status of the segment is changed to reflect the problem. The alert monitor also writes messages regarding the problem into the system log and into the self-monitoring functionality.
The CCMS_System_Segment is a special case. It is not the shared memory segment used for storing database monitoring information. Rather it is the shared memory area used for storing internal information of the alert monitor. Do not set it offline.
The first three statuses shown above are set automatically by the alert monitor. It tries periodically to gather information from each segment and sets the status according to the result. The offline status must be set manually. It remains in effect until the administrator changes it back to online.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
