How to maintain SAP Profile Parameters using

RZ10
Assumption
These steps are based on the assumption that you are familiar with
SAP BASIS technology and terminology for BASIS, Web AS (WAS) with
versions 610, 620, 640, 700 and 710 as well as SAP transaction code
concept.

Background
Profile files are read during the start-up of the SAP system and they are
located on the Operating System level. These files consist of Profile
Parameters with some assigned values. If some or any of the profile
parameters do not have a value assigned to it, it assumes the SAP
standard or default value.

Examples of parameters can be described as:

How many dialog work processes should be allocated to an SAP
instance?
What should be the minimum size for passwords?

All the above questions can be answered by specifying profile

parameter and assigning a value to it as shown below:
rdisp/wp_no_dia = 4 (means 4 dialog work processes are allocated for
each instance)
login/min_password_lng = 6 (means min size limit for password is 6
characters)
Note: Values can differ based on system to system and companies to
companies

There are 3 types of Profile Files:

Start Profile file, Instance Profile files and Default Profile file.
If you want to make global changes, i.e. changes that should affect all
the instances of an SAP system, those changes goes into the Default
Profile file. Any instance specific change should be entered in the
Instance Profile file
The profile parameters in the Start Profile file are usually system
related and it identifies the message server host, database name, etc
and we don’t make changes here unless required.
Remember the following:
Number of Default Profile File = One per System (SID)
Number of Instance Profile File = Number of Instances per SAP System
(SID)
Number of Start Profile File = Number of Instances per SAP System
(SID)
Transaction codes RZ10 and RZ11 are used to change the Profile
Parameters.

Important
Changes to Profile parameters (in the Profile files) take effect only
during the next start-up. The reason behind this is that the Profile files
are read only during the start-up. When you make changes to the
profile parameters in a started system (using RZ10), the instance does
not know the current or changed value unless it reads it next time
during the start-up.
There are however certain parameters (example:
rdisp/max_wprun_time etc) which can be changed dynamically using
RZ11 transaction and it takes effect right away. However during the
next start-up it will take the value from the Profile files on the
Operating System level.

The Profile Files follow this naming convention as shown below:

Default Profile File: DEFAULT.PFL
Instance Profile File: <SID>_<INSTANCENAME>_<hostname>
Start Profile File: START_<INSTANCENAME>_<hostname>
where : -
<SID> is your SAP system name, example “TOR”.
<INSTANCENAME> is your Instance name, example “DVEBMGS00”
<INSTANCENAME> is your Dialog Instance name, example “D10”
<hostname> is your machine name where SAP is installed, example
“sapserver”

Assuming example names above, these would be the names of the

Profile Files:
Default Profile File: DEFAULT.PFL
Instance Profile File: TOR_DVEBMGS00_sapserver
Instance Profile File: TOR_D00_ sapserver
Start Profile File: START_ DVEBMGS00_ sapserver

Note: The profile files are located on the Operating System level under
<drive>:\usr\sap\<SID>\SYS\profile (Windows)
/usr/sap/<SID>/SYS/profile (Unix)
Implementation Steps
1. Execute transaction RZ10 to get to the initial screen of Profile
Parameter Maintenance

2. From the Profile drop down, select the Instance profile file, in our
case “TOR_DVEBMGS00_SAPSERVER”. Select the “Extended
maintenance” radio button and click Change

3. In our example we would like to change the profile parameter

“rdisp/wp_no_dia”. We double click on that line to get into the
edit mode of that parameter
4. Change the value of the parameter in questions
(rdisp/wp_no_dia) from old value to the new value (in our case
from 5 to 6) and click on Copy button

5. Click Yes to save the changes

6. Verify that the parameter (rdisp/wp_no_dia) now shows the new
value.
On this screen click the back arrow button

7. Confirm the pop-up by choosing Yes to save the changes

8. On this screen, click the Save icon to finally save the Changes

9. Click Yes to activate the profile

10.Click the green check mark to confirm the activation on the
Operating System

11.Your profile changes have been saved and activated on the

Operating System level. These profiles will be in effect during the
next system start-up. Click the Green check mark to confirm the
screen.
Note: The profile files carry important profile parameters. Changes to these or some
parameters can have an adverse effect on the systems performance and sometimes the
system may not be able to start-up due to these changes. It is therefore necessary to back
these profile files before making any changes so you can roll back in case the system acts
funny after the changes to the Profile files.
When you make changes to the profile files using RZ10, it automatically creates a .BAK
file on the Operating System level. However if you manually make changes on the
Operating system level either using Windows utility or Unix vi utility, make sure that you
have a good backup of these files.