LS_TRC_SEVERITY (Parameter)

Parameter: LS_TRC_SEVERITY

Definition

The severity threshold for the generation of trace messages

Description and Use

Caution

Do not change the value of this SAP CC system parameter in a productive system landscape, except under the direct supervision of a support specialist from your SAP Support Team, or under specific recommendation provided within the SAP CC documentation.

Before changing the value of this system parameter, check the tracing domains that are enabled in your SAP CC system to verify the volume of traces.

This system parameter defines the severity threshold for generating trace messages to the configured destinations (see the LS_TRC_DESTINATION parameter). By default, the trace messages are generated to the logging destination fileset #2.

The main trace thresholds are:

ERROR (default and recommended): To use in a productive landscape; Only the trace messages associated to errors (incl. fatal) are generated by the SAP CC system.
INFO: To use in a development landscape Informational text, mostly for echoing what has been performed; This level is interesting for a development SAP CC system during the implementation phase of the integration project
PATH: To use for advanced troubleshooting operations only by a support specialist from the SAP Support Team

See the Syntax section for more information about the possible values, descriptions, and scopes.

Recommendation

SAP recommends that you use the default settings in a productive SAP CC Core Server system:

The SAP CC system generates the traces to the destination fileset #2
The trace severity threshold is set to ERROR
No tracing domain is filtered so the system records all the relevant traces

Use the reset command of SAP CC Admin+ to retrieve the factory settings.

Note

Similar parameters ( LS_APP_SEVERITY and LS_SYS_SEVERITY ) are available to set up the severity thresholds used for the generation of the log messages.

Caution

If no value is set for this parameter, the value of the "ls.trc.severity" system property located in the startup configuration file (jstart.config) of the instance is used instead.
If this system property is not set, the "ERROR" value is used instead.

Syntax and Constraints

Recommendation

Before changing the value of this system parameter, check the tracing domains that are enabled .

The possible values are:

Trace Severity Threshold	Description	Scope	Generated Traces by Severity
`DEBUG` (**)	All the trace messages are generated by the SAP CC system	This is the highest severity threshold for debugging purpose by SAP labs, with extensive and low level information	Debug, Path, Info, Warning, Error, Fatal
`PATH` (**)	All the trace messages are generated by the SAP CC system, except the debug traces that are dedicated to SAP labs or L3 support specialists.	For tracing the execution flow in the system (or Java Virtual Machine environment), e.g. used in the context of entering and leaving a method, looping, and branching operations	Path, Info, Warning, Error, Fatal
`INFO`	The SAP CC system generates: Trace messages associated to warnings and errors (incl. fatal) Informational text, mostly for echoing what has been performed	This severity threshold is interesting for a development SAP CC system during the implementation phase of the integration project	Info, Warning, Error, Fatal
`WARNING`	Only the trace messages associated to warnings and errors (incl. fatal) are generated by the SAP CC system.	This severity threshold is interesting for a test, quality assurance, or pre-production SAP CC system during the implementation phase of the integration project or during the operation phase. SAP CC application can recover from anomaly, and fulfill the desired task, but need attention from developer/IT integrator/IT administrator/operations team/support specialist.	Warning, Error, Fatal
`ERROR` (default and recommended)	Only the trace messages associated to errors (incl. fatal) are generated by the SAP CC system	This severity threshold is recommended for a productive system as there is a low volume of generated traces and important traces are available when there is an error. SAP CC application can recover from error, but cannot fulfill desired task due to the error. The experts from the operations team and the support specialists from SAP Support Team need all the error trace messages.	Error, Fatal
`FATAL`	Only the trace messages associated to fatal errors are generated by the SAP CC system	This severity threshold is not recommended. The SAP CC system generates only fatal error traces. SAP CC application cannot recover from error, and the severe situation causes fatal termination.	Fatal

Caution (**)

Once set to DEBUG or PATH level, the SAP CC system generates a high stream of several MB per minute. Check before if the file rotation mechanism is available or if you have only one single file in the destination fileset for traces or if you have customized the file naming by setting special values.

Additional Information

For more information, consult the product documentation of SAP Convergent Charging:

SAP CC Application Help (aka SAP CC Library) about the logging and the tracing functions
SAP CC Log Message Reference and Error Troubleshooting about detailed information for each log message, possible reasons, and follow-up activities (troubleshooting)
SAP CC Operations Guide about monitoring and troubleshooting

Technical Details

For more information, consult this section.

Name

LS_TRC_SEVERITY

The severity threshold for the generation of trace messages

Category Parameter

Type String

Access (RO/RW)

RW(+): Dynamic Read / Static and Dynamic Write

An immediate change is possible but is temporary. When it is relevant, change the permanent settings used by the SAP CC Core Server system when it restarts.

Use the Admin+ user interface to change the runtime values or the permanent values of this system parameter in an instance of the SAP CC Core Server system or in multiple instances.

Groups

System: Log and Trace Settings

Instance Types

This system parameter is available in the following types of instances in a running SAP CC Core Server system:

rater, updater, guider, bulkloader, taxer, dispatcher

Default Values (Factory Settings)

The predefined default values are:

Instance Type	Value
Rater	`ERROR`
Updater	`ERROR`
Guider	`ERROR`
Bulkloader	`ERROR`
Taxer	`ERROR`
Dispatcher	`ERROR`

You can use a default value to reset the runtime value or the restart value (persistent) in the Admin+ user interface.

Note

A default value is part of the factory settings of the SAP CC Core Server systems. It differs from the original value set during the installation or after the Customizing activities.

In Admin+, you can reset a parameter value to this default value, but it is not recommended:

This value may differ from the original value set during the installation of your SAP CC system.
Note that it may also differ from the value defined by the implementation project team and set during the Implementation Phase of the integration project.

Verify the values in your running SAP CC systems before to use the reset command.