Ansicht
Dokumentation

RZ11_DOKUMENTATION - RZ11 transaction documentation

  Parameter attributes

  ----------------------

  The parameter attributes and the parameter documentation should

  be entered using this transaction.

  The attributes of the profile parameter are used as the basis for

  checking the start, default and instance profiles within CCMS

  (Transaction RZ10).

  You can use the F4 Possible entries pushbutton to display the

  valid input values of the work area, the parameter type, the

  changeability and the valid operating systems.

  You can find detailed information on the values in the

  appendix.

  Parameter documentation

  ----------------------

  The documentation is entered in the logon language and

  translated accordingly.

  Documentation must be created for each profile parameter.

  This documentation is to be used as a basis for SAP documentation,

  which is displayed as F1 Help within the profile maintenance.

  You should always check the appearance of the documentation

  in display mode, as this is how the documentation is

  presented to the customer.

  The documentation should contain the following points:

   Parameter description

   Work area

   Parameter unit (Byte, KByte, seconds ...)

   Default value

   Who is permitted to make changes

   Limitations for operating systems

   Limitations for database systems

   Are other parameters affected or concerned

   Valid entries, restrictions etc.

  Printing the documentation

  -------------------------

  You can print the documentation for individual parameters

  as well as for all parameters.

  a) Documentation for individual parameters

     Enter the name of the parameter in the parameter name field

     and choose 'Print', or branch to the

     parameter documentation and choose 'Print' from

     there.

  b) Documentation for several parameters

     Enter the parameter you require in the Parameter name field

     using the wildcard character and then choose 'Print'.

     Parameter name = '*' means that the complete parameter

     documentation is printed.

  If the documentation does not exist in the logon language, the

  English documentation, if it exists, is printed.

  .

  Appendix : Documentation on the values

  ------------------------------------

  Short description:

  ------------------

  This should be short description of the parameter. This documentation

  should always be in English, as it is not translated.

  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 the parameter type does not have its own check routine

  defined.

  The following parameter types are currently defined:

  Integer :

  This is an integral value. In addition, you can specify a maximum

  and/or a minimum value.

  Example : rdisp/TRACE

  Error situations :

     a.) Non-numeric value                          -> Error

     b.) Greater than the maximum                   -> Error

     c.) Less than the minimum                      -> Error

     d.) Less than the default value from sapparam.c-> Error

     e.) 10 times greater than the default value    -> Warning

  Integer (64 Bit):

  This is an integer value, which is also suitable for

  64 bit integer values. The error situations are the

  same as for an integer value.

  Time :

  For the profile parameter, this is a time specification,

  usually a repetition period.

  Example : rdisp/btctime

  Error situations :

      a.) Non-numeric value                          -> Error

      b.) Greater than the maximum                   -> Error

      c.) Less than 0                                -> 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 :   0,1   ON,OFF   YES,NO   TRUE,FALSE



  Directory :

  This is a directory in the file system. There are no additional

  checks.



  Example : rdisp/workdir

  Directory must exist :

  This is a directory in the file system. This directory must

  exist.

  Example : DIR_EXECUTABLES

  Directory can be described :

  This is a directory in the file system. The directory must

  exist and can be described.

  Example : DIR_PROTOKOLLS

  File name :

  This is a file name. There are otherwise no additional checks.

  checks.

  Example : gw/secinfo



  File name must exist :

  This is a file name and the file must exist.

  Example : abap/rsyn

  File must be executable :

  This is a file name and the file must be an executable

  program.

  Example : exe/gwrd

  Character string :

  This is any character string. There are no additional checks.

  checks.

  Example : abap/locale_ctype

  Host name :

  This is a host name. The network software must recognize this

  the service.

  Example : rdisp/mshost

  Service name :

  This is a service name. The network software must recognize

  host name.

  Example : rdisp/msserv



  SAP service :

  This is an SAP service, whose name is composed according

  to SAP convention.

  The message handling system must recognize the SAP service.

  Example : rdisp/btcname



  File template :

  This is a file or a directory name that can contain placeholders

  that are replaced during runtime by valid values. There is no

  check.

  Example : FN_ATRAPATH



  Special character string :

  This is a special character string. The parameter should only

  contain particular character strings.

  Example : rdisp/bufrefmode

  In this case, the separator should be specified in a separate

  field.

  Changeability:

  --------------

  Changes allowed:

  The customer can make changes to this profile parameter.



  Change creates warning :

  The customer can make changes to this profile parameter. However,

  these changes can create problems if they differ from the

  SAP standard values.

  Example : rdisp/myname



  Change creates error :

  The customer should not make changes to this profile parameter.

  These can be profile parameters that were used to control

  particular actions.

  Example : transport/systemtype



  For all servers :

  ------------------------

  If this field is selected, the check will get

     the value of the parameter on every server and check whether

  the values are the same.



  Can be changed dynamically.

  ------------------

  If this field is selected, the value of the parameter can be

  changed dynamically, while the system is running.



  If the field is selected, the pushbutton "Change value" appears

  automatically. When you choose this pushbutton, a dialog box appears

  in which you enter the new value of the

 parameter.

  In the dialog box, you can select the "Change on all servers" field.

  The system will then change the value on all servers in the system.

  This field is automatically selected if the "On all servers" field

   is selected.



  If the value of a parameter was changed, an additional line appears

  indicating who changed the parameter and when.

  A system log entry is written as well.



  Default value

  -----------

  Default value of the parameter as defined in the kernel or

  default.pfl.



  Profile value

  ----------

  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

  --------------

  Parameter value currently used by the system.

  The value can change while the system is running.

  (See "Can be changed dynamically)



  Check routines :

  -----------

  In addition to the standard checks, you can define a form routine

  for the profile parameter check.

  Name of the form routine that should be called for the profile

  parameter check.

  All check routines should be in the include member LSPFCCHK.

  Here there is also a template for calling the form

  routine.

  Operating systems :

  ---------------

  The profile parameter is only valid for the operating system

  specified.



  You can enter the following :

  *                     No limitations

  UNIX                  All UNIX systems

  AIX                   IBM UNIX

  HP-UX                 HP-UX Unix

  OSF1                  Digital Unix

  SINIX                 SNI Unix

  SunOS                 Sun Unix

  Windows NT            Windows NT

  OS400                 OS400/AS400

  WIN                   Windows 3.x

  MAC                   Apple Mac

  OS2                   OS/2

  VMS                   OpenVMS AXP

  VAX                   OpenVMS VAX



------------------------------------------------------------------------ 

| Short Description : RZ11 transaction documentation 

------------------------------------------------------------------------ 



------------------------------------------------------------------------ 

| Applications Area : System 

------------------------------------------------------------------------ 



------------------------------------------------------------------------ 

| Parameter Type : S 

------------------------------------------------------------------------ 



------------------------------------------------------------------------ 

| Changes allowed : X 

------------------------------------------------------------------------ 



------------------------------------------------------------------------ 

| Valid for Operating System : * 

------------------------------------------------------------------------ 



------------------------------------------------------------------------ 

| Dynamic switchable :  

------------------------------------------------------------------------ 



------------------------------------------------------------------------ 

| Same on all Servers :  

------------------------------------------------------------------------