Parameter Properties
Transaction RZ11 can be used to display properties of profile parameters and to dynamically change the values of profile parameters. The properties of the profile parameter act as the basis for checking the default profiles and instance profiles in the system (transaction RZ10).
Metadata of Profile Parameters
Name
Name of Profile Parameter
Parameter Type
Assignment of a profile parameter to a type. For each parameter type, there is a standard check. This check is always executed if there is no separate check function for the parameter.
The following types are currently defined:
Integer
This is an integral value. A maximum and/or a minimum value can also be specified.
Example: rdisp/TRACE
Error situations :
a.) Non-numerical values -> error
b.) Larger than the maximum -> error
c.) Smaller than the minimum -> error
Double
This is a floating point number. A maximum and/or a minimum value can also be specified.
Error situations :
a.) Non-numerical values -> error
b.) Larger than the maximum -> error
c.) Smaller than the minimum -> error
Boolean
This is a switch with two statuses. Only the following values are permitted. All other values are interpreted as errors.
Example: gw/keep_process
Permitted values: TRUE, FALSE, 0, 1, ON, OFF, YES, NO. The comparison is not case-sensitive.
Character String
This is any character string. No check is made.
Example: abap/locale_ctype
Enumerations
These are enumerations. The parameter can only contain certain values.
Example: rdisp/bufrefmode
Restrictions
The parameter type can be restricted further:
- Parameter type Integer to a range with a minimum value and a maximum value
- Parameter type Double to a range with a minimum value and a maximum value
- Parameter type Character String to a fixed number of parameter values that can be chosen. For example, “DIA BTC UPD UP2 SPO ENQ”.
Unit
A parameter value can have a unit. The following units are available:
- Bytes
- Kilobytes
- Megabytes
- Gigabytes
- Milliseconds
- Seconds
- Minutes
- Hours
- Days
- Percent
Parameter Group
The parameter group describes the application area in which the parameter is used. The following values are defined:
- System
- Dispatcher
- Internet Communication Manager (ICM)
- Enqueue
- Message Server
- ABAP
- Background Processing
- Perf
- Syslog
- Spool
- Database
- Alert
- J2EE Engine
- GUI
Parameter Description
Short description of the parameter. Is always written in English, since this text is not translated.
System-Wide Parameter
If the parameter has this property, the value of the parameter is fetched on each server during the check and the system checks whether the values are the same. The value must be the same on all servers.
Dynamic Parameter
If the parameter has this property, the value of the parameter can be changed dynamically, that is, during running operation. In this case, a “Change Value” button is automatically displayed in RZ11. If the user chooses the button, a dialog box appears, in which he or she can enter the new value for the parameter. In the dialog box, the user can check the “Switch on All Servers” field. This means that the value is changed on all servers of the system.
Changes are recorded both in the syslog as well as in the change history. The change history contains the last 10 changes and is deleted with every restart of the server.
In addition to the metadata, rz11 also displays information as to the source of the current parameter value. If the value has been changed manually, the source is displayed as “dynamic switch”, together with a link for calling the change history.
In some cases, the current value can deviate from the profile value, although it has not been changed manually. These cases are also viewed as dynamic changes. However, since there is no change history here, the comment “(kernel)” is displayed instead of a link to the change history. One example of a parameter where this effect can occur is rsdb/max_blocking_factor. If the profile value is -1, the parameter value will be changed by the kernel to the default value of the database interface (see SAP Note 1296224).
Vector Parameter
If the parameter has this property, the parameter can be set more than once in a vector. Example: icm/server_port can be configured as icm/server_port_0, icm/server_port_1, and so on.
Has Subparameters
If the parameter has this property, the parameter value consists of subparameters. Example: icm/ssl_config has the subparameters CRED, CACHESIZE, LIFETIME, VCLIENT, and CIPHERS
Display the Current Values
Kernel Default
Default value of the parameter, as defined in the SAP kernel.
Default Profile
Default value of the parameter, as defined in the default profile DEFAULT.PFL.
Instance Profile
Value of the parameter, as defined in the instance profile. If the parameter is not defined in the instance profile, the default value is used.
Current Value
The value of the parameter as it is currently used in the system.
Origin of the Current Value
Relevant expansion hierarchy that provides the parameter value. This pertains solely to the parameter itself. In the case of formula parameters (such as rdisp/wp_max_no), which consist of multiple parameters, the values of the individual resolution levels can differ and still be displayed with origin “kernel default”. This is because one of the parameters used in the formula was set in the profiles.
