Many of the settings on how the system opterates are setup in a parameter file, very high level and with very interesting values. Check out report RSPARAM to list all values. Would you like to know how long your program can run before a TIME_OUT occurs ?

Run report RSPARAM which get's it's information from a C-call to C_SAPGALLPARAM, just because the information is too sensitive to allow some Abap programmer to trash the original file with these settings (which would stop the system).

If you need a parameter value - use function module RSAN_SYSTEM_PARAMETER_READ to pick it up. You need multiple parameters ? use function module RSAN_SYSTEM_PARAMETERS_GET.

Parameter documentation

Once you've found the parameter you are interested in, run transaction RZ11 "Display profile parameter attributes" to find out more about the parameter. It has a documentation button which explains what the parameter is for / how it works.

Maintenance and version management

If you do need to change a parameter, you could directly edit the source file, but you would be breaking quite a handfull of rules. The basis people could become a bit cross with you, for good reason. This is not an Abap matter - this is a Basis matter - make sure you involve them. Transaction RZ10 is a maintenance tool which also keeps track of old versions of the parameter file. It has a display option with a few views that group parameter settings together by subject, e.g. memory management, directories, languages and work processes / buffers. The transaction uses default profiles and instance profiles and a profile has it's own version management. So if you would like to know when a parameter was changed, RZ10 will tell you.

Parameter values: some examples

Here's some interesting values listed in (case sensitive) system parameters (note: there are hundreds, these are just listed to give you an impression of what can be found here):

• rdisp/max_wprun_time Maximum work process run time. The number of seconds that can pass before the TIME_OUT runtime error is raised.
• rdisp/max_alt_modes Maximum number of alternative modes. This controls the "Maximum number of sessions reached" message you may have seen a few times by now.
• rdisp/max_debug_lazy_time Maximum hold time for work processes in DEBUG mode. If you go for coffee while your debugger is running, the session will time out in the number of seconds defined here.
• rdisp/vbmail Send mail in case of an update error. An indicator that controls behaviour on update errors, there are many indicator settings too.

• Prev
• Next