Progress Startup Parameters by Versions - Forum - OpenEdge RDBMS - Progress Community

Progress Startup Parameters by Versions

 Forum

Progress Startup Parameters by Versions

  •  has updated my (12-year-old) list of Progress startup parameters and added the information about parameters in Progress versions upto 12.0.
    There are a lot of undocumented and "zecret" parameters. For some of them I found the description, others are still unknown.
    I hope this list of of Progress startup parameters may be useful.

    PrmByVer.2019.08.26.txt

  • Thanks George.  Do you have any more info about -retryAfterCatch?  I can't find any reference to it in NeRF, KB, or PDF or online docs.  

    Does anyone know if this is supposed to be a documented client startup parameter?  Or if the new behaviour of FOR blocks is documented somewhere?

  • Rob, the information about -retryAfterCatch is in OpenEdge 12.0 Release Notes:

    docs.progress.com/.../progress_oe_12.0_release_notes.pdf

  • Thanks.  Seems like a change that should also be in the NeRF.  And it's an undocumented param.  

    Can someone in the Content team log a doc bug please?

  • Just for fun: the number of startup parameters per Progress version:

    Num Version Release Date
    --- ------- ------------
    710 12.0.0  Feb 22, 2019
    702 11.7.4  Oct  9, 2018
    700 11.7.3  Apr 27, 2018
    669 11.7.2  Oct 24, 2017
    690 11.7.1  Jun 14, 2017
    689 11.7.0  Mar 27, 2017
    665 11.6.4  Oct  3, 2017
    664 11.6.3  Sep  8, 2016
    659 11.6.2  May 20, 2016
    654 11.6.1  Feb 16, 2016
    652 11.6.0  Oct 16, 2015
    634 11.5.0  Dec  5, 2014
    624 11.4.0  Jul 25, 2014
    609 11.3.3  Sep 25, 2014
    606 11.3.2  Jan 27, 2014
    606 11.3.1  Sep 19, 2013
    605 11.3.0  Jul 17, 2013
    600 11.2.1  Apr 29, 2013
    599 11.2.0  Feb 13, 2013
    592 11.1.0  Jun 15, 2012
    576 11.0.0  Dec  2, 2011
    577 10.2B08 Nov 12, 2013
    574 10.2B07 Sep  7, 2012
    572 10.2B06 Mar 19, 2012
    559 10.2B05 Sep  6, 2011
    559 10.2B04 Mar  8, 2011
    554 10.2B03 Dec  9, 2010
    549 10.2B02 Sep  1, 2010
    546 10.2B01 Apr 27, 2010
    546 10.2B00 Dec 14, 2009
    513 10.1C00 Feb  9, 2008
    497 10.1B00 Jan 10, 2007
    464 10.1A00 Dec 20, 2005
    418 10.0A00 Dec 13, 2003
    411  9.1E00 Oct 22, 2004
    391  9.1D00 May 15, 2002
    354  9.1C00 Jun 07, 2001
    330  9.1A02 Mar 22, 2000
    317  9.0B00 May 08, 1999
    316  9.0A03 Mar 06, 1999
    307  8.3E00 Jun  5, 2002
    303  8.3D00 Jan  8, 2001
    299  8.3C00 Apr ??, 2000
    295  8.3B00 Jan 29, 1999
    290  8.3A01 Aug 27, 1998
    281  8.2C00 Feb 23, 1998
    280  8.2A00 Apr 28, 1997
    265  8.1B00 May 17, 1997
    264  8.1A02 Dec  9, 1996
    253  8.0B00 Jul 10, 1996
    246  8.0A02 Mar 04, 1996
    225  7.3E02 Jun 11, 1997
    225  7.3C01 Oct 12, 1995
    225  7.3B17 Sep 27, 1996
    145  6.2M38 Feb 22, 1996
  • FWIW, the  -noclr No CLR (PAS for OpenEdge only) switch applies to all (Windows) clients, not just PASOE.
     
  • So George, only 710 startup parameters in version 12?

    How many do you think startup parameters are in Oracle?

    2913 in Oracle 11

    4846 in Oracle 12

    But 90% of them are hidden.

    Only 353 could be seen with V$PARAMETER in version 11 and 418 in version 12.

    Dmitri Levin

    Alphabroder

  • The count of records in _DbParams and the count of _DbParams-Is-Modifiable:

    11.5.0  98 21
    11.6.4 103 21
    11.7.0 119 33
    12.0.0 138 47

    Most of new db paramaters in 11.7 and 12.0 are modifiable. *)

    Version 12.0 fixed the wrong names of some parameters in _DbParams:

    -PendConnTimeout -> -PendConnTime
    -SQLTempStoreBuff -> -SQLTempBuff
    -SQLTempStoreDisk -> -SQLTempDisk
    -SQLTempStorePageSize -> -SQLTempPageSize

    Just for a note: -SQLTemp* db startup parameters were renamed in 9.1D06

    New in V12: the -H parameter reports a host name even if a database was started without the -H. In previous verisons the value was "Not Enabled".

    In V12 _DbParams lost the -diagProc. Other -diag* parameters are still available.

    Kbase # 000093101: OCTA-9735: "The database startup parameters -cpcoll ICU-fr -icucistr PRIMARY -collop 1 are not listed under the VST field _dbparam". 

    In OpenEdge 12.0, the _DbParams VST replaces the _Startup and _Statbase VST tables from previous versions and have been removed.

    *) New versions aslo changed the _DbParams-Is-Modifiable attribute to yes for some old parameters.

  • PrmByVer.txt file in the first post is updated with the list of the parameters introduced in 11.7.5 (plus other minor changes).

    11.7.5 as of Jun  7 2019
    ------------------------
    
    + -defrdlogentrytypes <list>
    + -defrdlogginglevel <0-???>
    + -defrdlognumlines <n>
    + -zDontFlushErrors
    
  • /* V11.5+ */

    for each _DbParams no-lock by _DbParams-Msg-Num:

     disp

       _DbParams-Id format ">>9" label "id"

       _DbParams-Name format "x(20)"

       _DbParams-Value format "x(30)"

       _DbParams-Is-Default   label "Default"

       _DbParams-Is-Modifiable label "Modify"

       _DbParams-Msg-Num format ">>>>9" label "MSG".

    end.

    Dmitri Levin

    Alphabroder

  • 12.1 as of Aug 26, 2019

    + -defrdlogentrytypes A single entry or comma delimited list of logging entry types for the deferred log buffer.
    The default is the 4GLTrace log entry type.
    See docs.progress.com/.../Use-deferred-logging-in-PAS-for-OpenEdge.html
    or $DLC/servers/pasoe/conf/openedge.properties.README


    + -defrdlogginglevel Logging level for messages into the deferred log buffer.
    0 - No log file written
    1 - Error only
    2 - Basic
    3 - Verbose
    4 - Extended

    + -defrdlognumlines <n> The maximum number of lines of log information that may be written to the deferred log buffer, shared by all ABL sessions in an agent.
    The default value is 0, which disables the feature.

    + -dynqrySSJ <n> Dynamic Queries Server-side Join? Parameter is not supported by a login broker.
    Release 12.1 is enhanced to perform server-side joins for dynamic queries. Certain queries that join multiple tables are now resolved in the database server rather than the client. The dynamic query server-side join capability is available in a multi-threaded database server for certain queries containing up to 10 tables in the same logical database. At this time server-side joins for dynamic queries are limited to queries that are FORWARD-ONLY, with NO-LOCK.

    + -zDontFlushErrors Related to a deferred logging?

    + -zdsreuse

    Database startup defaults changed - various startup parameter defaults are updated to improve the overall performance of the OpenEdge database. The impacted parameters are:

      Parameter        Old   New value
      -aibufs           20    64
      -bibufs           20    64
      -lruskips          0   100
      -lru2skips         0   100
      -pica            64K  128K
      -prefetchDelay     0     1
      -prefetchFactor    0   100
      -prefetchNumRecs  16    64
      -prefetchPriority  0     1
      -Mm             1024  8192
      -Mxs             16K   32K

    The consistency checks can be enabled on more granular level:

    -AreaCheck    Area block consistency check in area "" (-AreaCheck):  (14017)                | Only one -AreaCheck may be specified. (15383)
    -TableCheck Record block consistency check in table "", partitionID (-TableCheck):  (14019) | Only one -TableCheck may be specified. (15384)
    -IndexCheck  Index block consistency check in index "", partitionID (-IndexCheck):  (14018) | Only one -IndexCheck may be specified. (15385)

    2 old parameters are now reported by _DbParams: -cstackPrintopt and -diagProc

    38 old algorithmic db startup parameters became modifiable in 12.1:

    Ver   Mod _DbParams
    12.1.0 85 140
    12.0.0 47 138
    11.7.5 43 128
    11.6.4 21 103
    11.5.0 21  98

    Increasing parameters that require the resources:

    Expected for OE 12.1: -ecsize, -secsize, -numCheckPointStats
    but not implemeted.

    History and the plans:

    10.2B %s increasing lock table size (-L) from %i to %i. (13979)
    10.2B %s increasing buffer pools size (-B) from %i to %i. (13980)
    10.2B %s increasing bi buffer pool (-bibufs) from %i to %i. (13981)
    10.2B %s increasing ai buffer pool (-aibufs) from %i to %i. (13982)
    10.2B %s increasing excess shared memory (-Mxs) from %j to %j. (13983)
    11.4  %s increasing object mapping cache (-omsize) from %l to %l. (17732)
    11.7  %s increasing CDC cache size (-cdcsize) from %j to %j. (18608)
    
    12.1  %s increasing encryption cache size (-ecsize) from %i to %i. (19454)
    12.1  %s increasing security cache size (-secsize) from %i to %i. (19455)
    12.1  %s increasing maximum number of users (-n) from %i to %i. (19456)
    12.1  %s increasing table statistics limit (-tablerangesize) from %i to %i. (19471)
    12.1  %s increasing index statistics limit (-indexrangesize) from %i to %i. (19472)
    12.1  %s increasing user table statistics limit (-usertablerangesize) from %i to %i. (19473)
    12.1  %s increasing user index statistics limit (-userindexrangesize) from %i to %i. (19474)
    12.1  %s increasing lob statistics limit (-lobrangesize) from %i to %i. (19484)
    12.1  %s increasing user lob statistics limit (-userlobrangesize) from %i to %i. (19485)
    12.1  %s increasing pica queue size(-pica) from %i from %i. (19506)

    Typo: from %i from %i. (19506)

  • "Expected for OE 12.1: -ecsize, -secsize, -numCheckPointStats

    but not implemeted."

    Changing -numCheckpointStats online was implemented in 12.1, but the way to change it is not through increaseto. Instead, it can be changed through _DbParams VST and PROMON's Adjust Startup Parameters screen.

  • Increasing the size of -ecsize and -secsize is implemented in 12.1.  The can be increased using proutil -C increaseto.
     
    -jeff
     
  • > Increasing the size of -ecsize and -secsize is implemented in 12.1

    Sorry for misleading. Yes, it's implemented. Mea culpa - too many Progress windows were opened during the tests.

  • > Changing -numCheckpointStats online was implemented in 12.1, but the way to change it is not through increaseto. Instead, it can be changed through _DbParams VST and PROMON's Adjust Startup Parameters screen.

    The used bytes in Shared Memory Segments is the exactly same no matter what the value of the -numCheckpointStats was used to start a database. In other words, Progress seems always to allocate the memory for the max value (-numCheckpointStats 1024) - at least in 12.1. So the increasing of the -numCheckpointStats online does not required an additional memory. But the increasing (from 1 to 1024) the -numCheckpointStats through _DbParams increases the used shared memory by 160 bytes. It's a bit strange, isn't it?