RZ11: SAP Profile Parameters

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 parameters act as the basis for checking the default profiles and instance profiles in the system.

Metadata of Profile Parameters

• Name
  • Name of the profile parameter

• Parameter Type
  • Assignment of a profile parameter to a type. A default check is associated with each parameter type. This check is always executed if there is no separate check function for the parameter. The following types are currently defined:
    • Integer
    • Double
    • Boolean
    • Character string
    • Enumerations
  • 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:
    • Byte, kilobyte, megabyte, gigabyte
    • Milliseconds, seconds, minutes, hours, days
    • Percentage

• Parameter Group
  • The parameter group describes the application area in which the parameter is used. The following values are defined:
    • Abap, Alert, Batch, Database, Dispatcher, Enqueue, Gui, ICM, J2EE Engine, Perf, Spool, Syslog, System

• 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.

• 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

• Internal Parameter
  • This parameter is intended for special cases only, such as troubleshooting or other internal purposes. In most cases, it should be set in a production system.

• Read-Only Parameter
  • This parameter can be read by other parameters but should not be set in the profile file. The kernel default should be used instead. The kernel default may be platform-specific.

• Recommended Value
  • Some parameters have a recommended value that is not the same as the default. This is because the default is no longer recommended but cannot be changed for compatibility reasons. If it were changed, the system behavior would also be changed automatically.
  • In new installations, the recommended value is written to the profile automatically.

Display the Current Values

• Kernel Default
  • The default value of the parameter, as defined in the SAP kernel.

• Default Profile
  • The 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 refers only 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.