The generated parameter file contains a unique header followed by reusable parameters. The generated file lists all of the startup parameters, but comments out the parameters that are not explicitly needed to maintain the configuration of the running system.

OpenEdge classifies startup parameters into five processing categories, depending on how their settings affect your configuration. The generated parameter file formats each category of unused parameter with a unique comment indicator, so that you can tell at a glance how changing the parameter affects your system.

You can sort the parameters in two ways:
  • Ordered by the _DbParams row ID. (Lower case letters sort before upper case.) This is available only when you use PROMON to generate the file.
  • Grouped by category
The following generated parameter file groups parameters by category: 
###############################################
#
# OpenEdge generated DB parameter file.
#
# Database name:    /usr1/theDBdir/demo
# OpenEdge version: 12.8.0.0
# Date generated:   [2023/05/18@10:59:53.519-0400]
#
###############################################
#
#     Parameters explicitly set
#     -------------------------
-db "/usr1/theDBdir/demo"
-hostnameAliasing
-limitLgPayload 1
-B 100000
-L 100000
-H PFG-Demo-Host
-S 6987
#
#
#     Parameters set to default value
#     -------------------------------
#    -aibufs 64
#    -baseindex 1
#    -baselob 1
#    -basetable 1
#    -baseuserindex 1
#    -baseusertable 1
#    -bibufs 64
#    -biscantime 10
#
#     Parameters with auto generated default value
#     --------------------------------------------
##   -hash 25621
##   -lkhash 13063
##   -pwscan 166
##   -spin 12000
##   -Ma 5
#
#     Parameters with no specific default value and not explicitly set
#     ----------------------------------------------------------------
###  -aiarcdir ""
###  -aiarcinterval -1
###  -bithold 0
###  -clstmtcachedir ""
###  -diagDir ""
###  -lgArchiveDir ""
###  -omitLgMsgs ""
#   
#     Parameters requiring no value and not explicitly set
#     ----------------------------------------------------
#### -aiarcdircreate
#### -aistall
#### -bistall
#### -directio
#### -i
#### -lgArchiveEnable

The following table lists the comment indicator and describes the behavior of parameters in each category:

Category Comment indicator Description Notes
1 None Parameters explicitly set at broker startup Quotation marks enclose all the name values that allow special characters.
2 # Parameters with the default value These parameters are commented out so that, if the default values are updated in a new release, the deployment can use the updated values without changing anything. If they were not commented out, the currently set value have overridden a new default value.
3 ## Parameters with autogenerated default value

These parameters are commented out with two number signs (##) to indicate that they are the default value based on their associated parameter and that they have not been overridden

For example, if you increase the value of –B, the –hash automatically changes based on that.

If you change –B online, the current value for –hash changes.

Normally, a parameter that is not the current default appears as an explicitly requested parameter. However, this is not the case with autogenerated parameters.
4 ### Parameters with no specific default values

These parameters were not requested at startup and have no associated default value.

You cannot remove the comment unless you specify a value for each of these parameters.
5 #### Parameters that were not requested but take no value

These parameters are listed to indicate that they exist but that they have neither been specified nor enabled.

Be careful when editing these parameters, because removing the comment changes the behavior of the running configuration; in some cases, drastically.