Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CCM-MON (Application Component) Monitoring⤷
SMOI (Package) CCMS: Monitoring Architecture
Basic Data
| Data Element | ALKEEPLNTY |
| Short Description | Alert: MSG Container: Keep lines type |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | INT4 | 4-byte integer, integer number with sign |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 11 | |
| 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 | KeepLinTyp |
| Medium | 16 | Keep lines type |
| Long | 20 | Keep lines type |
| Heading | 0 |
Documentation
Definition
Specifies how the monitoring architecture should manage the storage for logs or traces (log monitoring attributes).
Space for holding the messages that are reported to log attributes is inherently limited. This specification tells the alert monitor what to do if the number of messages that has been reported exceeds the space available or space allocated.
The choices you have are as follows:
- Keep as many messages in the log as possible. Use this option for very important logs or traces, when you want to keep as much of the log available as possible.
In this case, the alert monitor lets the number of messages in the log grow above the limit specified by the user in ALKEEPLNMX.
The growth of the log is then limited only by the space available in the monitoring architecture's shared memory area. The log is allowed to take up all of the space available until another user of the shared memory area needs space. If this situation occurs, then the size of the log is scaled back and messages are deleted, oldest messages first. To calculate the number of messages to delete, the monitoring architecture finds the difference between the number of messages actually held in the log and the limit specified by the user (ALKEEPLNMX). The alert monitor then deletes one-half of this number of messages in order to release shared memory.
- Keep newest messages up to the limit specified in ALKEEPLNMX. In this case, the log always holds the newest messages, in chronological order.
- Keep oldest messages up to the limit specified in ALKEEPLNMX. In this case, the log always holds the oldest reported messages. New messages are deleted (though messages texts are retained in any alerts triggered by the messages).
This option applies only to log attributes in which the monitoring architecture provides the log management functionality. This option does not apply to log attributes that refer to the SAP system log or to external logs.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in |
