Progress Startup Parameters. =========================== Last update: Jun 18, 2019 by George Potemkin (G.Potemkin@progress-tech.ru) Notes. ===== 1. The list contains server and client startup parameters as well as parameters for some Progress utilities. 2. Where it is possible I will narrow down the origin of parameter to the Progress patch number. 3. Plus(+) sign after Progress version means that parameter was introduced in that release. Minus(-) sign respectively means that parameter was obsolete. 4. Abbreviation "pkb" refers to a Progress knowledge base article. Abbreviation "msg" refers to a Progress message number. Acknowledgements. ================ The Progress Email Group was a great source of information for creation of this document. Several people have been kind enough to share their knowledge: Dmitri Levin Geoff Crawford Grant Maizels Bob Brennan Libor Laubacher Pedro Martinez Stefan Marquardt Kraa de Simon Lee Curzon Undocumented Parameters of the Releases before V7.3B. ==================================================== 6.X + -, European Numeric Format (the same as -E) 6.X + -PF Parameter File (the same as -pf) 6.X + -! Fast Track Message File Fast Track Message File contains any text data. The bounds of the data records are defined by an index table stored in the file header. You can refer to any record by the include file syntax {!}. Msg ## 1722-1725 say: The -! feature is a temporary feature for Version 6 PROGRESS only. It WILL NOT be supported in future version of PROGRESS. De facto, this feature is available up to V9. 6.X + -ct Specify how long the client will wait and gather SPX information on the CONNECT. The -ct option is a connection parameter. Issue #20000721-001, Patch 1st Fixed: 8.3C07 on Win32 6.X + -synchronous Enables Synchronous Debug Mode. 6.X + -Mxs Shared Memory Overflow Size. Default: -n * 300 bytes. 6.X + -I Total Private Buffers. Pkb 5633 Default: 2 * -n, Range: 0 - 32000, Type: Broker Parameter PROGRESS tries to use private buffers for read-only operation thereby reducing competition for shared buffers; In V7/8/9 PROGRESS still allocates the private buffers. Set -I 0 in startup.pf. 6.X + -O Private Buffers Default: 0, Range: 0 - (-I), Type: Connection Parameter 6.3 + -nap Nap Time / Initial Latch Sleep Time Default: 10 ms before V7.3C and 20 ms in V7.3 and up. Range: 10-500 ms. When a process is trying (-spin tries) to acquire a latch and fails then it naps -nap ms. See promon -> R&D -> 'debghb' -> Administrative Functions -> Adjust Latch Options -> Initial latch sleep time. 6.3 + -napinc Nap Time Increments Default: 2 times The nap time is multiple by a value of the -napinc when a process naps -napstep times (i.g. 20,40,80,160,...). 6.3 + -napmax Maximum Nap Time (pkb 16518) Default: 5000 (100 with V7.3C-??? - Progress bug, it should be 5000). The maximum value to which a nap time can increase. 6.3 + -napstep Maximum Increment Steps When a process naps -napstep times the nap time is increased by a value of the -napinc. 6.3 + -lkhash Lock Table Hash. Default value is a prime number greater than 1/8 the -L value where the prime number is sourced from an internal PROGRESS array (30 entries) from 13 to 98407 with values increasing in a geometric progression using the approximate ratio 1 to 1.4. The prime number table is identical in versions 6.3, 7 and 8. The same table is used for the -hash parameter (pkb 15385). Each entry uses 12 bytes of the shared memory. Pkb 15956 or 16580. 6.3 + -ixlru Index Block LRU Recycle Limit Default value: 0, Range: 0-99 This is an experimental feature that is designed to give index blocks preference over data blocks in the buffer ageing algorithm. The idea is that when index block finds its way to the tail end of the lru chain, we put it back on the front and let it age again before replacing it. The recycle limit controls how many times it gets to go around. See: promon -> R&D -> debghb -> Startup Parameters Set: promon -> R&D -> debghb -> Administrative Functions -> Adjust Page Writer Options -> Index block recycle limit 6.* -z -z output to see if it did any temp file writes (it should not). 6.2 + -z1 Force a crash (for test purposes) between commit phases with 2PC. CONNECT db1 -db db2 -z1. 6.3 + -znohint Turn off ALL hints sent to ORACLE; Pkb 16306 6.3 + -znotrim Don't trim trailing blanks in where clause. ORACLE DataServer; Pkb 13078 5.X + -zod Don't use ORACLE TRUNC for date in where clause; Pkb 12384. 6.X + -zo Shows SQL code that Progress generates and sends off to ORACLE. The -zo is not supported in V7.3C+. In V8 this feature has been replaced with query tuning paramter qt_debug (-Dsrv qt_debug,SQL). 6.2 + -zp Issue a message 1408: The id of this process is . 7.3A + -zcache Issue a message 821: Reading schema cache for database... 7.3A + -zr Ignore R-Code File / Forces Session Compile. Msg 2887 7.3A + -zqil Query Index Listing (msg 1848). Local character clients only. (But kbase #21216 says that -zqil and -zqilv are working in GUI/CHUI and with local/remote connection). Details: http://www.geocities.com/d_levin/dlc/zqil.html or: http://techweb.progress.com/kbase/21216 (Some notes about undocumented parameters -zqil & -zqilv) 7.3A + -zqilv The same as -zqil parameter but with LEAF info. 7.3A + -zn Disable the special meaning of the leading underscore ("_"). By default: - Progress does not allow to create the temp-tables, fields, variables, etc with the names begining with "_". - For the procedures with names beginning with "_" Progress applies the same rule as for all procedures when -q parameter is used. 7.X + -m4 prosql: oidrvr32.exe -SV -S -m4 -Mi -pf 7.X + -cgw Compatible R-Codes (Oracle DataServer). V7: Deals with the queries that use ORACLE tables with a progress_recid column (Pkb 17397). The procedures compiled with (without) -cgw must be run with (without) -cgw (Msg 2721, 2722). V8: To generate r-code with a Version 8.0B client that an 8.0A client can also run, you must specify the Compatible (-cgw) parameter when you start your 8.0B session to compile and save the r-code. If code references DATE columns that are mapped to the CHARACTER data type, you will not be able to generate compatible r-code, even if you specify -cgw. 6.X only -K Keystroke Capture/Playback. Pkb 5985. Record keystrokes: -K record Interactive Playback: -K playback keyfile.mstr keyfile.gen Batch Playback: -K batch keyfile.mstr keyfile.gen where is your master file originally recorded, is where the results of playback will be stored. TERM environment variable must be the same as what you set to record. 7.3A + -QA Quality Assurance Layer (Character mode only) Record keystrokes: -QA record Play back the keystrokes: -QA playback Report window creation: -QA log -QA option sets the time in seconds since the start of the UNIX epoch to 0. The start of the UNIX epoch is 00:00 1/1/1970 GMT. Connection Parameters (that define an process to connect to). ============================================================ 7.X + -SV Open Interface Driver Connection The -N,-H,-S,-m2,-Mm,-nb,-NL,-Nv,-pp parameters followed the -SV parameter belong to OIB/OID. If a Parameter File (-pf) startup parameter is included in the -SV parameter list, all parameters in the file, up to the first -db parameter, are part of the -SV parameter list. However, all parameters after and including the first -db in the parameter file are ignored, and are not passed to OIDs. 6.X + -Gw Directs PROGRESS to shut down DataServer Broker. Msg 3663. Ie. the -N,-H,-S parameters followed the -Gw parameter belong to a DataServer Broker. 8.1A + -AS Directs PROGRESS to shut down AppServer Broker. Pkb 16288. ie. the -N,-H,-S parameters followed the -AS parameter belong to a AppServer Broker. 8.1A + -web WebSpeed Broker Connection Ie. _wta -web -wtbname -wtbport -wtaminport 9.0A + -svub Indicates using unified broker service. See below. Changes by release. ================== 7.3B as of June 1995 -------------------- 7.3B + -ininame Initialization File 7.3B + -brl Bleeding Record Lock (pkb 13881, 15160) 7.3B + -dictexps Dictionary Expressions 7.3B + -checkdbe Check Double-byte Enabled 7.3B + -nocheckdbe No Check DBE 7.3B + -cpprint Printer Code Page 7.3B + -cprcodein Read Rcode Code Page 7.3B + -cprcodeout Write Rcode Code Page 7.3C01 as of Oct 12 1995 ------------------------ No changes. 7.3E as of Apr 17 1997 ---------------------- No changes. 7.3E15 ---------------------- 7.3E15 + -tcponly Prevent the NLM server from starting up the SPX protocol. Pkb 19632 8.0A as of Nov 1995 ------------------- 8.0A + -cplog Log File Code Page 8.0A + -fldisable Field List Disable 8.0A + -noindexhint Index Hint 8.0A + -nojoinbysqldb Server Join 8.0A + -noSQLbyserver SELECT Pass Through Disable 8.0A + -OUTPUT Redirects the output from a Progress batch session to a file. Pkb 16768. 8.0A + -rbcpreportin Report Code Page In 8.0A + -rbcpreportout Report Code Page Out 8.0A + -rbcpudfin UDF Code Page In 8.0A + -rbcpudfout UDF Code Page Out 8.0A + -rbdel Report Engine Record Delete 8.0A + -rbfile Report Engine File -rbfile rbrun.txt This can be used when running prore.exe from the command line. _printrb.p must first be run to generate the rbrun.txt. This is intended for internal testing only. 8.0A + -rbP Encoded Password (documented in V9) 8.0A + -rbstatfile Report Status File 8.0A + -rbtable Report Engine Table Name 8.0A + -rbtag Report Tag 8.0A + -rbupds Report Update Status 8.0A + -SQLlogging OID Server Connection (OID, AppServer) 8.0A + -zpfnet ? 8.0A + -zbfs ? 8.0A + -zfl Field List Reports (msg 4164, 4165) Writes to a database log file debugging messages about re-reading a field-list records and reports a number of records read. 8.0B as of Jul 10 1996 ---------------------- 8.0B -spin PROGRESS implemented -spin on NT (Michael Furgal) 8.0B -directio Became supported on all platforms (Michael Furgal) 8.0B + -basekey Registry Base Key 8.0B + -evtlevel Event Level. There is EVTLEVEL environment variable. 8.0B + -hardlimit Hard Limit for -D,-nb,-mmax,-l. Pkb 16387 8.0B + -mux 0 Turn off mtlkmux() and mtfrmux() when -spin has been set. Msgs 3717, 3718, 5797. 8.0B + -portnumber ? Obsolete in V8.1A 8.0B + -znosavepoints No Save Points 8.1A02 as of Dec 9 1996 ----------------------- 8.1A - -portnumber Introduced in V8.0B. 8.1A + -AS Directs PROGRESS to shut down AppServer Broker. Pkb 16288 8.1A + -con Connect Procedure 8.1A + -dis Disconnect Procedure 8.1A + -lkwtmo Lock Time Out 8.1A + -logfile Log File (compserv.lg) 8.1A + -logname Event Name 8.1A + -Mpte Shared Memory Page Table Entry Optimization Digital UNIX. Msg 5556. Rewritten in V8.3A. 8.1A + -trace Trace (AppServer) 8.1A + -web WebSpeed Agent Connection 8.1A + -weblogerror WebSpeed Agent should create an error log file 8.1A + -wtamaxport Agent Maximum Port Number 8.1A + -wtaminport Agent Minimum Port Number 8.1A + -wtbport Broker Port Number 8.1A + -zcompsrvrbuf ? 8.1A + -znw ? 8.1C06 as of Jul 06 1998 ------------------------ 8.1A03-8.1C06 + -ASID [AppServer Server Startup parameter] A sequence (instance) number for the Appserver / the server thread ID. Example from KB-21454 S-0001>Server exec error : CreateProcess: "C:\Pro91\bin\_proapsv.exe" -ubpid 368 -Ms 1 -logname asbroker1 -logfile "C:\PROGRESS\WRK\asbroker1.server.log" -ASID 1 -ubpropfile "C:\Pro91\properties\ubroker.properties" -svrefresh -ASID 1 => S-0001 8.2A as of Apr 28 1997 ---------------------- 8.2A -Mpte VLM64 Page Table Entry Optimization (Digital UNIX) Syntax was changed: an argument is not need anymore. 8.2? + -exact Allows a procopy to be made without the changes to the master block. Pkb #16676. 8.2A + -blocksize Block Size (PROSTRCT Utility) 8.2A + -groupdelay Group Delay (Turning tips: pkb 18003) 8.2A + -index Index (PROUTIL DUMP Qualifier) 8.2A + -Mpb Maximum Servers per Broker 8.2A + -maxport Max Dynamic Server Port 8.2A + -minport Min Dynamic Server Port 8.2A + -Mms AAppServer Maximum Maintained Prestart Counter 8.2A + -Ms AppServer Maximum Prestart Counter 8.2A + -populate Disable Fast Schema Changes 8.2A + -nopopulate Enable Fast Schema Changes 8.2A + -norecover Disable DB Recovery with Off-line Backup. Pkb 17553 8.2A + -tscope ? 8.2A + -zprofile Profiler Config File: http://www.peg.com/utilities.html 8.2B ---------------------- 8.2B + -verbose (proutil -C idxfix -verbose) Send the output to standart out instead of .lg file. Does not work until V8.2C. 8.2C as of Feb 23 1998 ---------------------- 8.2B-8.2C + -noreorder No Join Reorder (Report Builder, pkb 19119) This option may help increase performance on reports that contain SQL using the implicit join syntax. 8.2C + deactivate Deactivate indecies (proutil -C load deactivate) 8.2C09 as of Sep 03 1998 ------------------------ 8.2C09 + -nofixdate From: Brian K. Maher To: peg@peg.com Subject: PATCH: 8.2C07 for Win32 (95,NT) Date: 10/08/1998 Progress failed to properly adjust a date format using 4 digit years when using the -d ydm, -d dmy and -d mdy startup parameters. Date formats will now be rearranged to correspond to the -d startup parameter. The -nofixdate startup parameter can be used to disable this change if required. --- The -nofixdate parameter resolves the memory violation problem with the code: DEFINE VARIABLE v-date AS DATE. MESSAGE "Enter date" UPDATE v-date. --- Date: 24 Nov 1998 From: mattg@progress.com (Matt Gilarde) Subject: Re: Update date field on message line To: peg@peg.com The MESSAGE UPDATE bug has been fixed in a recent 8.3A patch. There should be no need to use -nofixdate once you have the patch. Matt Gilarde - PSC Development --- 8.3A as of Aug 05 1998 ---------------------- 8.3A -noshm No Shared Memory on Server. Obsolete. Starts a single server for a database rather than a broker. The clients can connect to a database only using the -H, -S parameters. In V8.3/9.0 the connection ends with the errors: The server or the system has no more resources. Try a larger -n. (748) ** Server rejected login. (700) 8.3A + -bistall BI File Threshold Stall 8.3A + -bithold Recovery Log Threshold. The value is rounded down to the nearest cluster (Britt Johnston) Before Image Threshold must be at least 3MB. Starting in V9 the upper limit of -bithold: 4GB * (biblocksize / 1k) 8.3A + -indexbase Index Base 8.3A + -indexlimit Index Limit 8.3A + -tablebase Table Base 8.3A + -tablelimit Table Limit 8.3A + -semsets Semaphore Sets (-semsets is not a valid argument on NT/Windows. It is being ignored.) 8.3A + -p21 Prophet 21 for C-ISAM Dataserver. Obsolete in V9.0A 8.3A + -rbfilenodel Don't delete p#####RB.TXT file (V8.3B readme.wri) 8.3A + -rbexpjoins Forces RB to use explicit join syntax for inner joins (readme.wri) 8.3A + -rbclearxactions Pkb # 17016: When printing or previewing a new transaction is started. This new transaction will not end unless a new startup parameter is used. This new parameter is -rbclearxactions and should be specified on the command line where Report Builder is started or in the rbstart.pf file. 8.3A + -rbzsqldump This will create a log file c:\foo\sql.log which contains all of the ESQL generated by Report Builder for a report. The directory c:\foo must exist before Report Builder is run with this parameter. This is also intended for internal testing only. (Angela Albert from PSC Tech Support) 8.3A + -rbcltoolong ? 8.3A04 as of Oct 19 1998 ------------------------ 8.3A04 + -rbtabledb Specify which database contains the RBREPORT table (or whatever table is specified with the -rbtable parameter). Pkb 19145, V8.3B readme.wri. 8.3A04 + -portableframes Portable Frames Portableframes was an attempt to make for portable r-code across operating/windowing systems. If you have shared frames and compile your code on different platforms (a.p compiled on machine1, b.p compiled on machine2), and you don't use -portableframes, you will have errors*). There is another error if you do use the option under 8.3B. Glen West (gwest@physio-control.com) --- *) Bug 98-09-15-066: Shared frame layouts do not match for frame . (683) 8.3B as of Jan 29 1999 ---------------------- 8.3B -maxport Applied to Application Broker (not in V8.2 - pkb 18382) 8.3B -minport Applied to Application Broker 8.3B + -apsvnap ? Obsolete in V9.0A 8.3B + -devevent ? Obsolete in V9.0A, re-added in V9.0B From: "Resperger Josef" To: Date: Dec 18, 2000 Starting with Release 9.1 there is a significant change in the behaviour of "return no-apply" which is not the same on every machen and it seems to be different between runtime and development version. We have been running into that. They suggested that we use the -devent Startup Parameter (not documented) and this helped! 8.3B + -rereadnolock Re-read No-Lock (pkb 19063) Patches 8.3B07 and 9.0B04 fix the bugs (issue# 19990408-006, 19990617-017) caused by the -rereadnolock parameter when you use a browser. 8.3B12 (AIX), 8.3B14 (Win32) --------------------------- 8.3B + -Msc Allows correct messaging between OID and small client. Issue #19980706-005: -Mm 16000 will core or GPF when using SQL select statements. 8.3BXX --------------------------- 8.3B + -noshvarfix ? Exist in V9.1A as well Pkb #20235, Definition of the -noshvarfix parameter In version 7 progress never instantiated any defined shared variables that were not referenced in the program. For example, if you defined 20 shared variables and only assign 3 of them, Progress would only have instantiated those 3. Now in Version 8 because of bug 19950124-041 there is certain circumstances when we need all the shared variables instantiated such as Persistent Procedures. Because of this issue the fix was made to instantiate all variables whether they are assigned or not. Even though this fixed the persistent procedure problem it created another problem. Because we now instantiate all variables, we began to receive performance complaints from customers trying to upgrade from V7 to V8. Their programs were taking longer to run in V8 than in V7 because of the instantiation of all variables. So we created the fix for this bug (19990713-048). A patch was created for 8.3B that added a client startup parameter -noshvarfix to 'turn off' fix for 19950124-041. 8.3B2X + -tgb Proutil -tgb -C dump The tag -tgb splits the .bd file when it reaches 2000000000 bytes. (thanks to Stefan Marquardt). Issue #19991116-034 Alpha OSF creates binary dumps larger than the 2 GIG limit. This makes porting the dumped file to a "smaller" platform impossible. 8.3C ------------------------ 8.3C + -Moi [OID/OIB Startup parameter] Set max size of the messages that OID can send to a SQL89 client. Use the CLSDMSG environment variable to set a size of the client's messages. 8.3C01 (Compaq Tru64), 8.3C03 (Sun Solaris) as May 04 2000 ---------------------------------------------------------- 8.3C + -noinactiveidx Prevent the compiler selecting inactive indexes. Issue # 20000405-004 Pkb 19825: Starting a client session with this parameter will force the compiler to only select active indexes when compiling source code. This removes the need for an index to be deleted from the database when trying to control the indexes that are selected by the compiler. 8.3D as of Jan 08 2001 ---------------------- 8.3D + -fixcurtable ? 8.3D + -wrttries WebSpeed Agent Retries (see V9.1B below) 8.3D + -wrttrypause WebSpeed Agent Try Pause (see V9.1B below) 8.3D04 + -nocore The -nocore option will allow for no core files to be created Vol 3, Ed 3 08-33023 System Hangs with Core Files in NFS Drive If a core file is created on an NFS drive, you might find that the system hangs and does not allow any other user or process to access the NFS drive. These core files are large and can take more than three minutes to write. 8.3E as of Nov 15 2001 ---------------------- -ojmode 1|2 OUTER-JOIN Mode -ossilentfix Issue #20010712-007 When running probuild, you may receive an error such as: Unresolved: argossilentfix -PendConnTime Pending client connection timeout 9.0A03 as of Mar 06 1999 ------------------------ 9.0A ACCESS=all It's the default for all databases started with ProControl and the AdminServer (Mike Furgal). 9.0A - -apsvnap Introduced in V8.3B 9.0A - -devevent Introduced in V8.3B, re-added in V9.0B 9.0A - -p21 Introduced in V8.3A 9.0A - -portableframes Introduced in V8.3A04 9.0A -Nv Network Version. Introduced in V6.2F. 12 (for V5/V6 database) is the highest (and the only) number you can use. 20 (for V7 database) is not supported. Pkb 18900 9.0A -rptint License Usage Reporting Interval RN#: 091B-00216 Progress Explorer erroneously allows you to set the Reporting Interval property (-rptint) for database configurations. This property is not supported by the Progress V9 database. 9.0A -a After-Image File Name. The -a parameter is only valid with rfutil -C roll forward. 9.0A -g Before-Image File Name is obsolete, 9.0A -blocksize Block Size (PROSTRCT BUILDDB Utility) 9.0A - -indexbase It's a first time when PSC renames the parameters! 9.0A - -indexlimit ... and lose a way in V9.1 9.0A - -tablebase 9.0A - -tablelimit 9.0A + -baseindex Index Base Replace -indexbase 9.0A + -indexrangesize Index Range Size Replace -indexlimit 9.0A + -basetable Table Base Replace -tablebase 9.0A + -tablerangesize Table Range Size Replace -tablelimit 9.0A + -f Location of AdminServerPlugins.dat (pkb #21080) 9.0A + -port Main AdminServer listening port, where all queries, and start/stop requests are sent. By default, this is port 20931. 9.0A + -adminport Used by databases to communicate with the AdminServer (together with -servergroup). By default, this is port 7832. Pkb #19360 V9.1 doc says that -adminport was introduced in V9.0B. 9.0A + -AppService Application Service Name 9.0A + -Bp Private Read-only Buffers 9.0A + -classpath SQL-92 Server Java Classpath 9.0A + -DataService Data Service. Connect a client through a NameServer to the broker. See also the -nonameserver parameter. 9.0A + -debugalert Sets SESSION:DEBUG-ALERT to YES. Documented in V9.1. 9.0A + -list Obtaining Storage Area Descriptions Using PROREST 9.0A + -m5 [Misc Servers parameter] KB-P98830: What does -m5 mean? It is a value that has always been a part of our product, but never documented as it is one that is not meant to be used externally. It is essentially an internal parameter that we reserve for certain functions related to server processes. You will sometimes see this referenced in many different circumstances, such as on the adminserver, on the _dbagent for Fathom, on remote servers (_mprosrv, _sqlsrv2) spawned by the login brokers. It is similar in functionality to the -m1, but the presence of which is neither one that raises a need for concern, nor one that should ever be used. 9.0A + -nonameserver The same as -DataService "none". . ReadEng.hlp: For diagnostic purposes only, it is acceptable to bypass the NameServer connection and connect directly to the broker instance. To do this, specify the reserved DataService name "none" as follows: -DataService none 9.0A + -omsize Storage Object Cache Size (msg 8527) Use -omsize to specify the number entries in the secondary storage object cache. At startup, a primary and secondary storage object cache are allocated, each with the number of entries specified by the -omsize startup parameter; INCREASETO only modifies the size of the secondary cache. 9.0A + -profile Profiler Config File (enhanced -zprofile). See %DLC%\src\samples\profiler\readme.doc 9.0A + -properties (Copy of) Configuration Properties File (conmgr.properties) Used by *config utilities to validate the copy of Configuration Properties File. Ignored by proadsv. Check -propertyfile introduced in V9.1. 9.0A + -relative Suppresses conversion of a Relative Path Database with a procopy/prorest. By default, new database'll have the full paths embedded. Note: prodb = procopy -silent -relative. 9.0A + -servergroup Server Group Name No Stored Procedures if DB Started Using Progress Explorer RN#: 091A-00533 On Windows NT, if the Database is started from Progress Explorer, it is impossible to create or execute a stored procedure. The stored procedure can be created if the Databases have been started from the NT command line. Starting the Broker from the command line using the -servergroup and -adminport arguments will allow the Broker to be managed by the AdminServer. Use the db, configuration, and servergroup names that were created with the Progress Explorer, and the default value of 7832 for -adminport. Example: proserve -servergroup mydb.myconfig.myservergroup -adminport 7832 9.0A + -svrefresh [AppServer Server startup parameter] Example from KB-21454 S-0001>Server exec error : CreateProcess: "C:\Pro91\bin\_proapsv.exe" -ubpid 368 -Ms 1 -logname asbroker1 -logfile "C:\PROGRESS\WRK\asbroker1.server.log" -ASID 1 -ubpropfile "C:\Pro91\properties\ubroker.properties" -svrefresh 9.0A + -svub Indicates using unified broker service ReadEng.hlp -> Index -> 3.6.1 Configuring in the Explorer Framework on NT 8. To continue configuring the broker, choose the Server Parameters tab and provide the required information: Server Parameters - The -svub parameter is required for a broker connection in the Progress Explorer framework. 4.2.5 Starting the DataServer in the Explorer Framework and Connecting a Client If you do not set the required -Dsrv SVUB,1 and optional -DataService data-service connection parameters as described in this section, the client is assumed to be configured for a standard Progress broker and the -H and -S parameters are used to locate a probrkr executable on the appropriate host machine. By setting the SVUB parameter on, you redirect the -H and -S parameters to locate the appropriate NameServer and/or broker for the Progress Explorer on the host machine. 9.0A + -ubpid UBroker PID no. needed by agents at startup 9.0A + -ubpropfile UBroker properties file name (ie. ubroker.properties) 9.0A + -Wb ? 9.0A + -wss Windows Single Session 9.0A + -wtainstance Web Agent instance number, needed when starting agent 9.0A + -wtbname WebSpeed Broker Name as specified on broker's startup with the -i parameter. Used to start a WebSpeed Agent or to pass back to the name server. 9.0A + -yr4def Date Default Format with Four Digit Years (pkb 18505) 9.0A + -z92 ? 9.0A + -zallowdlc Allowes to connect (at command line only) to a database in $DLC. Otherwise you'll get the message 1379. 9.0B as of May 08 1999 ---------------------- 9.0B + -devevent ? Exist from V8.3B, deleted in 9.0A 9.0B -basetable Default is now set to 1. 9.0B -tablerangesize Default is now set to 50. 9.0B -baseindex Default is now set to 1. 9.0B -indexrangesize Default is now set to 50. At run time, you can change the table base or the index base: e.g. find first _StatBase. assign _TableBase=51 _IndexBase=21. 9.0B02-9.0B15 (9.0B11 as of Sep 15 1999 - for Win32) ------------------------ 9.0B + -nolkctr Issue # 19990910-030: To alleviate the problem of a large number of error 395's (warning - pcondb for db %s has lkctr %d) being written to AppServer log file, introduce a startup parameter to turn off error 395. 9.1A02 as of March 22, 2000 -------------------------- 9.1A - -baseindex V9.1 drops the V9.0 set of parameters and re-introduced the V8.3 set. 9.1A - -basetable Bug number 20000523-004 9.1A ? -indexrangesize V9.1 drops them on Windows and still support on Unix 9.1A ? -tablerangesize 9.1A + -indexlimit 9.1A + -tablelimit 9.1A + -addcomp Add Components (setup.exe) 9.1A + -indexbase V9.1 re-introduced the V8.3 set of parameters. 9.1A + -tablebase See note above. 9.1A + -propertyfile Configuration Properties File (ubroker.properties). Used by proadsv. The *config utilities still use the -properties parameter. 9.1A + -asyncinterval ? 9.1A + -asyncqueuesize Async Queue Size (AppServer's client). 9.1A + -C Used with SQLDUMP / SQLLOAD utilities to specify the code page of the dump file / the database utility. 9.1A + -extents PROSTRCT UNLOCK utility. Replaces missing extents with empty extents if any database files are missing. 9.1A + -isnoconv Initial Value Segment No Convert. (Compile-Time) Each initial value or :U string that contain non-ASCII characters add 8 bytes to a r-code action segment if the r-code was compiled without the -isnoconv parameter. The strings with the same length but with ASCII characters only produce an action segment as if the r-code was compiled with the -isnoconv parameter. RN#: 091A-00121 INIT strings and :U strings are codepage converted if they contain non-ASCII characters. It is possible that compiling existing code may result in larger r-code segments and compilation may fail due to exceeding segment limits. There will be no change if the strings are all ASCII. To turn off the new behavior, a new command line option, "-isnoconv", standing for "Initial value Segment NO CONVERT", has been added. 9.1A + -noshvarfix Described in 8.3BXX section. 9.1A + -numdec Fractional Separator 9.1A + -numsep Thousands Separator 9.1A + -ttwrdrul Temp-table word-break rule (undocumented). Default value is the default rules (0). 9.1A + -wtbhostname nnn.nnn.nnn.nnn [Webspeed Agent startup parameter] Webspeed Transaction Broker hostname KB-P95738: The process ID of the WebSpeed agent shows wrong IP address associate with the -wtbhostname The ubroker.properties file is copied from another machine where the UUID for the WebSpeed broker was generated using genuuid script. When used genuuid script, the first part of the UUID composed of the IP address of the machine where the genuuid script is run. Therefore, the IP address in the first part of UUID was visible for the *-wtbhostname* in the process ID of the WebSpeed agents KB-P39900: What is a quicker way to see how many agents are running? ps -ef |grep _progres |grep wtbhostname|wc -l 9.1A + -zgenkwlist Generate keyword list. In DOS (important!) prompt run: prowin32.exe -zgenkwlist > keywords.txt (Thanks to Julian Lyndon-Smith and Simon L. Prinsloo) 9.1A + -znnic No Null in Index Components RN#: 091A-00677 * For the DataServer for ODBC As of 9.1A, the DataServer for ODBC can perform data retrieval against any data source that allows nulls in a component that is used to identify an index. Prior to version 9.1A, the default behavior was to require that all components used to identify an index not be null. To restore this behavior you can use the -znnic startup parameter to start a Progress client or self service session. The -znnic startup parameter is not documented in Chapter 4 of the DataServer for ODBC Guide nor is it documented in the Startup Command and Parameter Reference or online help. It is described in the topic "Unknown Values and Sorts," in Section 2.2.3 of the DataServer for ODBC Guide. * For the DataServer for SQL Server The DataServer for SQL Server can perform data retrieval against any data source that allows nulls in a component that is used to identify an index. The default behavior allows nulls in any component that is used to identify an index. To switch the default behavior so that it requires that all components used to identify an index not be null, use the -znnic startup parameter to start a Progress client or self service session. 8.3C, 9.0B38, 9.1A16 and 9.1B -------------------------- -ojmode 1|2 OUTER-JOIN Mode -ojmode 1 - the inner join behavior predominated for the most part. -ojmode 2 - the outer join predominate (thus more records were included in the combination of outer/inner join than before). 9.1B as of August 17, 2000 -------------------------- 9.1B + -useOsLocale Causes Progress to set the Date Format (-d), Fractional Separator (-numdec) and Thousands Separator (-numsep) attributes based on the current Windows locale settings. 9.1B + -nohostverify No Host Verification while connecting to Web-enabled AppServers. RN#091B-00145 When you are connecting to a SSL enabled AppServer, you will get an error during the authentication of the Server Certificate resulting in: "-55 error code: Connect HostName: does not match Certificate (9318)". To workaround this problem specify the -nohostverify option on the URL connect statement. In V9.1C -nohostverify does not work until patch #11 9.1B + -noinactiveidx Prevent the compiler selecting inactive indexes. Pkb 19825 Two new startup parameters that allow a 4GL client to connect to an AIA or AIA/S mediated AppServer through a local firewall. 9.1B + -proxyhost Proxy Host specifies the host name or IP address of an HTTP-based proxy server 9.1B + -proxyport Proxy Port specifies the port on which the HTTP-based proxy server is listening. RN#: 091B-00225 A client started with the -proxyhost, -proxyport startup parameters (in order to use a proxy server) will fail to connect to a Secured Socket Layer (SSL) enabled web server. Upon issuing the connect, the client will appear to hang and eventually will time-out with the following error message "Secure Socket Layer (SSL) failure. error code 5: SSL certificate handshake error (9318)". 9.1B + -SS Sort File Directory Specification (proutil -C load build indexes) 9.1B + -URL Connect to AppServer using AIA. If the -URL connection parameter is specified, the -H, -S, and -AppService parameters are ignored. The -URL parameter allows you to specify AppServer connections using the following protocols: HTTP, HTTPS and AppServer. 9.1B + -wrttries WebSpeed Agent Retries (? Exists in V8.3D 9.1B + -wrttrypause WebSpeed Agent Try Pause (?) I guess both parameters are related to the kbase #21009 WebWrite() error 6404 http://techweb.progress.com/kbase/21009 This error message indicates that a problem occurred in the WebSpeed agent while attempt to send data to the WebSpeed messenger, this could be caused by the messenger process dying or a problem in the socket connection, when the agents detects the write() , it retries to send the information just to check if the problem was temporal, if the communication "wakes up" again, then the message is delivered , if not then you'll see a lot of messages about the retries in the log file of the agents. 9.1B01 + -extravc Revert to old value-changed behavior - if user selects currently selected browse row, value-changed trigger fires. Issue #20000922-033. Kbase 22047, New -extravc Startup Parameter 9.1B02 + -origbrowsel Pkb #20899, New -origbrowsel Startup Parameter: In version 8, it was possible to make a multiple selection in a read-only browse by clicking on the rows. However in version 9, you have now to press the CTRL key in order to achieve it. Since the patch version 9.1B02, a new client startup parameter (-origbrowsel) has been added in order to ensure the version 8 behaviour could still be used. Patch 9.1B02, Issue #20000625-007: A browse widget with multiple selection no longer allows the user to click a row with the mouse to select/deselect it. When the user does this the browse deselects all other rows and selects the row the user clicked on. 9.1BXX + -nocore The -nocore option will allow for no core files to be created Vol 3, Ed 3 9.1BXX -zod Compile-time parameter, Oracle DataServer (Pkb #20826, 20985) This will prevent the DataServer client from adding unique_id_0 to the ORDER BY when the ordering is due to a USE-INDEX or the index is chosen by the 4GL compiler. This has the potential of producing unexpected results if the value is not unique in the table. The -zod session parameter will suppress the entire ORDER BY clause a join that would not otherwise be ordered at compile time. 9.1B1X + -PendConnTime Pending client connection timeout Issue #20010329-003 - IPQoS scan breaks Broker load balancing. Msg 10357: It indicates the maximum time in seconds the broker will wait for a remote (-S) client to connect to the server it was assigned, before it will release the resources being reserved for the client. Pkb #20905, -PendConnTime parameter for Database Server 9.1C as of Jun 7, 2001 -------------------------- 9.1C + -Bpmax Maximum private buffers per user It indicates the per user maxumum number of private read-only database buffers currently configured for use by the database broker. 9.1C + -expandbrow Sets the FIT-LAST-COLUMN attribute to TRUE for each browse in that session. Is overridden by NO-EMPTY-SPACE attribute for an individual browse. 9.1C + -fixcurtable ? 9.1C + -maxxids Size of global transaction table (Database Broker) Since maxxids must be a multiple of 64, it may be different than what was specified on the command line. Exchange Identifier (XID) is an eight digit number which usually begins 05D, and identifies the Physical Unit associated with the control point. 9.1C + -nozgrouping [Client Session startup parameter] Stops all windows in a PROGRESS session being brought to the front when focus is given to a window. This was to allow you to keep lots of windows open, whilst still being ableto see your internet, market data, excel data etc. 9.1C + -opaque 0|1 The value of 0 turn the option off and 1 turns it on. The default value is 1 (ON). About -opaque was introduced because of the problems with VALID-HANDLE Function over WinY2K causing troubles with the handles (see Kbase 20363). Now the -opaque has been introduced for forcing always progress to returns you a handle number generated by progress, not by the OS. So the parameter is only needed if you think there is a bug caused by having it on. In that case you can turn it off and see if the bug goes away. Of course, if turning it off fixes the bug, it still does not tell us much since memory is arranged differently with and without the parameter. You can tell if opaque handles are in use in a session by creating an object and looking at its handle: DEF VAR H AS HANDLE. CREATE BUFFER H FOR TABLE "CUSTOMER". MESSAGE H. If h is a small number like 1001 or 1002 etc., then it is an opaque handle and not a direct memory address. References: 20363, VALID-HANDLE, Persistent Procedures, UNIQUE-ID and Win 2000 16355, Problems with Persistent Procedures and Valid-Handle. 15673, PROCEDURE : UNIQUE-ID attribute is unique value for session RN#: 091C-00239, Widget handles recycled on Windows You cannot use n = 0 on 64-bit machines where only opaque handles are supported. 9.1C + -prowcapp WebClient Application (.prowcapp) file. 9.1C + -zdlc Webclient installation directory (prowc.exe - Webclient Initializer) Pkb #20814, Webclient : unable to open message file: PROMSGS http://techweb.progress.com/kbase/20814 Pkb #20498, Webclient application does not start http://techweb.progress.com/kbase/20498 The format of the command line used to start the Webclient application is: "" 9.1C + -zwclog WebClient log file? 9.1C -debugalert Now supported in batch mode, WebSpeed Agents, and AppServers If developers run a non-interactive client with the -debugalert parameter, they can see the Progress 4GL-stack trace for the current Progress session in the procore file. 9.1C08 as of 2001/09/21 ----------------------- 9.1C0X + -ossilentfix ? When running probuild, you may receive an error such as: Unresolved: argossilentfix 9.1C0X + -baseADE Allows developers to specify the location of ADE r-code. Progress will add this directory and all of the .pl's in that directory to PROPATH at startup INSTEAD of adding %DLC%/gui(tty) and the .pl's from %DLC%/gui(tty). 9.1C0X + -noutf8warning Startup param to disable utf-8 warning. Issue #20010919-036 9.1C1X + -AdminMsgTimeout Specifies the time in seconds the broker will wait for a response after sending the adminserver a connection request message. The existing 10 second timeout will be the default and only values in the range of 10 to 900 seconds can be specified. Useful when autostarting up a lot (20+) of databases from the AdminServer. 9.1C1X + -browcoltype If specified, browse-column type returns "BROWSE-COLUMN" else it returns "FILL-IN". Issue #20011220-015 9.1C1X + -lbimod [0|1|2] [Client Session startup parameter] Use the "-lbimod n" startup parameter to keep the dbimage up to date with the lbi file. 0 just the same as before 1 fixes bug 20010625-003 2 fixes both 20010625-003 and 20011106-008 Please note that each increased value is more restrictive then the previous value. THIS NEW OPTION SHOULD NOT BE USED UNLESS ONE OF THESE BUGS ARE A PROBLEM We keep pointers into the lbi file in memory, in the record buffers whose records have been written to the lbi file. If you update the same record multiple times, you do not want multiple copies of it going into the lbi file. So if the record has already been written once during the current accept/reject unit (DO, REPEAT etc. block), then an lbi note referring the the earlier image is used, instead of the an lib note with the entire record. The bugs that came up had to do with nulling those pointers into the lbi file. The pointers were being nulled a little too late in some cases. This left the in-memory pointers pointing into the lbi file to a place that had already been either committed or rejected, and thus to garbage. Also, sometimes the pointers would simply be out-of-date, pointing at the wrong image. -lbimod 1 makes us go back over all the in-memory buffers and null out any pointers that point beyond the new endpoint of the lbi file whenever we reset the lbi endpoint to some position earlier than what it was -- e.g. after a commit or reject, to prevent any possible pointing into garbage. -lbimod 2 makes us reset a given buffer's in-memory lbi pointer to the latest version of a change whenever we before-image an update, so it can't end up pointing at some earlier update. And of course, -lbimod 2 includes the functionality of -lbimod 1 (-lbimod 2 is a superset of -lbimod 1). Setting to 2 is "stronger" than 1 (if set to 1 didnot help). Solutions P4133, "omIDToarea called with 0 Objectnumber" error occurs in Data P8598, Memory Violations occurs with "omIDToarea called with 0 objectNumber" 9.1D as of May 8, 2002 ----------------------- 9.1D -pwqdelay [Database Broker startup parameter] Determines how often the APW queue is checked, in milliseconds. The default is 100 milliseconds. The gist of what we did was to change the clock rate which governs the apws cycle of sleeping and writing dirty blocks from the checkpoint queue. Before, it was measured in multiples of seconds. Now it is in 100 ms cycles. You can use -pwqdelay to make the cycle time shorter if necessary. I have no evidence at this time to indicate it should be smaller. 9.1D -URL AppServerDC:{//host[:port]} [AppServer basic connection param] An HTTP or HTTPS-based URL to an AIA, or an AppServer-based URL to an AppServer that you connect to directly or through a NameServer. 9.1D + -admingroup group[:group...] [AdminServer startup parameter] Authorization with the AdminServer. To perform AdminServer functions, the user has to be a valid account in one of the groups. 9.1D + -clientlog [Client Session parameter] Name of log file used for messages and 4GL stack trace information (-debugalert). All error messages and messages that would normally appear in an alert box will also be written to the specified file. In addition to the message, some additional information, including time-stamp and process id will be written in the log. On connect and disconnect from a DB, an entry will appear in the client log file identifying the DB and UserID (For multi-user connections). This information can be used to relate log messages with DB log messages. Solutions: P45054, What does the -clientlog parameter accomplish? P5706, -clientlog parameter has no effect 9.1D + -DBService [replagent | replserv] [Database Broker startup param] Pre-register a DB Service. When the database server was started one or more database services were started as well (-DBService service). Connections to this database will not be allowed until all of these service have completed their startup and initialization work. E.g. -DBService replagent instructs the broker to start the Fathom Replication agent. 9.1D + -DirectConnect [AppServer basic connection parameters] If specified, the -H and -S parameters are interpreted as the network address and TCP/IP port number of an AppServer connection. Otherwise, the -H and -S parameters are interpreted as the network address and UDP port number of a NameServer. 9.1D + -ERO [Database Broker startup parameter] Enhanced Read-Only mode. If a database is started in enhanced ready-only mode the clients cannot updates the database. 9.1D + -filterocxevents [Client Session parameter] Filtering Asynchronous COM Events. By default, asynchronous COM events are handled when any of the following conditions occur: 1. While an application is waiting for user input, such as during a WAIT–FOR or UPDATE statement. 2. While an alert box from a MESSAGE statement is on the screen. 3. During trigger processing, if the MultitaskingInterval parameter is set to a number greater than 0. Handling COM events during the second and third conditions might cause random problems in your application, depending on what 4GL code is executed in the event trigger. You use the –filterocxevents startup parameter to prevent asynchronous COM events from being handled during the second and third conditions. 9.1D + -icfparam [Client Session parameter] Dynamics Parameter. You can access this string using SESSION:ICFPARAMETER attribute. 9.1D + -logappend [0|1] [Client Session parameter] Specifies if a new log file should be created even if the file specified by -clientlog exists, or if the log entries should be appended to the log file. Possible values: 0 - create new broker log file 1 - append to the existing log file Default: 0 9.1D + -logentrytypes [0-2] [Client Session parameter] Specifies the type of information recorded when performing diagnostic logging. This property should be set to 0 unless directed by PSC TS. Possible values: 2 - 4GL Tracing The parameter is changed in V10. http://www.progress.com/support/smartnews/aug02.htm#5 Starting in 9.1D01 (and later Service Packs) and 9.1E there is a new diagnostic feature that will record the execution of the following 4GL statements in a log file: * RUN * User-defined FUNCTIONS * PUBLISH * SUBSCRIBE The 4GL Tracing is enabled when the logginglevel parameter is set to 4, and the logentrytypes parameter is set to 2. To set these parameters: Specify the startup parameters -logginglevel 4 -logentrytypes 2, for GUI / TTY clients. For example: prowin32.exe -clientlog mylog.lg -logginglevel 4 -logentrytypes 2 or set srvrLoggingLevel to 4 and srvrLogEntries to 2 in the ubroker.properties file, for AppServer and / or WebSpeed instances. For example: srvrLoggingLevel=4 srvrLogEntries=2 9.1D + -logginglevel [0-4] [Client Session parameter] Specifies the amount of information to be written to the -clientlog file. Possible values: 0 - None 1 - Error only 2 - Basic (Terse) 3 - Verbose 4 - Extended (Diagnostic) In V10 you can read/set the value using LOG-MANAGER:LOGGING-LEVEL attribute. 9.1D + -logthreshold [Client Session parameter] Use Log Threshold (-logthreshold) to specify the file size threshold of log files. When the current log file becomes equal to or greater than the specified size, OpenEdge renames and saves the log file and creates a new log file. 0 — This means there is no limit other than what the operating system imposes. Value range: 0 or between 500000 and 2147483647 (bytes). Default value: 0 The logThreshold property is not used in V9.1D. The value should always be set to 0. In V10 you can access the value using LOG-MANAGER:LOG-THRESHOLD attribute. Also see the -numlogfiles parameter in V10. 9.1D + -md5mode 1|2 [Compiler Session parameter] The implementation of the MD5 Message-Digest Algorithm used by Progress Software Corporation in certain of its products is derived from the RSA Data Security, Inc. Generate-MD5 Compile Option Will Generate a Different Value Between 9.1C and Later Versions for the Same Code RN#: 091D-00296 =============== When you use the compiler option GENERATE-MD5=yes in 9.1C, the MD5 value generated was based solely on the expanded source code being compiled (i.e., the .p or .w file including all the include files). Starting in 9.1D the MD5 hash value will take other things into account, such as the schema of temp-tables or temp-table fields that are defined LIKE a database table or its fields. Therefore, if you upgrade from 9.1C, even if you do not modify your source code, but you do recompile with GENERATE-MD5=yes, the MD5 value for each file will change. Since the Application Assembler bases its decision of whether to include a .r in an update .CAB on whether the MD5 value has changed, it will determine that all recompiled .r code has been modified. Thus all such .r code will be re-deployed to your WebClient end-users with your next application version. You can avoid having this happen by running Progress with the following new startup parameter when it is run to compile your application code: -md5mode 1 This will cause the compilation to revert to the 9.1C algorithm and only take the source into account when generating the MD5 hash value. However, it is recommended that at some point you accept the default behavior so that you are guaranteed that schema changes that affect your .r's will cause re-deployment of those .r's. Specifying -md5mode 2 will give you the new behavior. Since this is the default, there is no need to use the startup parameter at all to get the new behavior. You can access the MD5 value stored in an r-code file using RCODE-INFO:MD5-VALUE attribute 9.1D + -nochkttnames [Client Session parameter] No Check Temp-table Names. Use the No Check Temp-Table Names (-nochkttnames) parameter to suppress the limited checking of temp-table column names when passing temp-table as parameters to procedures. 9.1D + -pi [replserv | replagent] Enables database for site replication. Msg 10519, 10356: You must first used the proutil command to enable site replication: proutil -C enablesitereplication [source | target] 9.1D + -pica Allocates storage for the IPC queue between ROCKET and replication. The larger space the less time the ROCKET will spend waiting for Replication. Default value: 4 9.1D + -pids Allocates additional resources for DB Service manager. The DB Service cannot be started at this time. (9871) 9.1D + -pinshm [Database Broker startup parameter] Pin Shared Memory will prevent the database engine from swapping shared memory contents to disk. Using this parameter will cause the database manager to create shared-memory segments that cannot be paged out. They are "pinned" in memory. Note that on Solaris, since version 8, we have been using a shared memory option called "initmate shared memory" or ISM, in addition to changing how TLB registers are used for shared memory, also has this same effect, so -pinshm is not required on Solaris. I initially wanted it to be the default, but eventually decided against it because: 1. One Solaris system we tried it on crashed unless you had an os patch. And you don't need it on Solaris anyway. But maybe there are other systems that also need patches. I don't know of any and we didn't run across any during testing -- but we can't test every version of every os with and without all the patches. 2. If you have an existing installation where shared memory /is/ being paged, and you have a many databases on the same machine, it could cause the application processes to be paged even more, and might make things worse. Figuring out what is going on would be /very/ difficult. While I think this is unlikely to happen, there are so many different environments and configurations out there that we decided off was a better choice. HOWEVER: The risk of bad side effects is small, and I still think it is a good idea to turn it on. It is a good preventive measure. Paging shared memory i/o buffers is a horrible thing: if you are reading something from the database into memory, having to read the buffer from the pagefile first is a complete waste of time and disk I/o. Similarly, having to read a chunk in from the pagefile in order to write it to the database is not good. Paging almost anyhting else is almost always better. 9.1D + -pmpf [Unknown] A wild guess: Plugin Manager Property File (pmmgr.properties)? 9.1D + -proxyUserid [Client Session parameter] User-id used to authenticate an AppServer client to the HTTP-based proxy server. The value can be accessed using SESSION:PROXY-USERID attribute. 9.1D + -proxyPassword [Client Session parameter] Password used to authenticate the AppServer client to the HTTP-based Proxy server. The value can be accessed using SESSION:PROXY-PASSWORD attribute. 9.1D + -qsize [Socket connection parameter] The length of the pending-connection queue — that is, the maximum number of connection requests you want the server to queue while it processes the connections already accepted. If the queue is full when a connection request is received, it is refused. The default length of the queue depends on the platform. 9.1D + -ServerType [4GL|SQL|Both] [Login Broker parameter] Type of Server to Start. There is ServerType in conmgr.conmgr.properties but it does not restrict access to broker when defined in Progress Explorer. Bug #20020920-010 fixed in V9.1D07. Solutions: P24369, What does -ServerType parameter do ? P7843, How to configure a secondary SQL92 Broker for Progress 9.1D 9.1D + -SQLCursors [SQL92 Login Broker parameter] SQL Server Max Open Cursors. -SQLCursors requires 9.1D06 or higher. Instead use OPEN_CURSORS environment variable. Value range: 16 - 512. Default value: 50. See 9.1D06 for details. 9.1D + -SQLMa [SQL92 Login Broker parameter] Maximum SQL Clients Per Server (msg 10020). The default is the maximum number of users (-n) divided by the maximum number of servers (-Mn). 9.1D + -SQLMi [SQL92 Login Broker parameter] Minimum SQL Clients Per Server (msg 10021) Default is 1. 9.1D + -SQLStack [SQL92 Login Broker parameter] Documentation refers it as the -SQLStackSize parameter. Size of SQL-92 Stack that is an internal memory area used by SQL program modules and allocated to each thread. Value range: 1000 - 2000. Default value: 1000 (KBytes). Increase if O/S complains of using too much stack Settings can cause unnecessary paging if set too high. The value can be set as PROGRESS_STACK_MIN environment variable. 9.1D + -SQLStmtCache <# of statements> [SQL92 Login Broker parameter] Documentation refers it as -SQLStmtCacheSize. The number of prepared statements to be stored in SQL Stmnt Cache. -SQLStmtCache requires 9.1D06 or higher (solution P24543). Instead use CACHED_STATEMENTS environment variable. Value range: 16 - 1024. Default value: 100 (statements). See 9.1D06 for details. 9.1D + -SQLTempStoreBuff [SQL92 Login Broker parameter] Size of SQL Server temp table buffer. In V9.1D06 it's replaced by the -SQLTempBuff parameter. Instead use TPE_MM_CACHESIZE environment variable. Value range: 100 - 200000. Default value: 1000 (KBytes). 9.1D + -SQLTempStoreDisk [SQL92 Login Broker parameter] Size of SQL Server temp table disk storage. In V9.1D06 it's replaced by the -SQLTempDisk parameter. Instead use TPE_MM_SWAPSIZE environment variable. Value range: 5000 - 100000000. Default value: 500000 (KBytes). 9.1D + -SQLTempStorePageSize [SQL92 Login Broker parameter] Size of SQL Server temp table data page. In V9.1D06 it's replaced by the -SQLTempPgSize parameter. Instead use TPE_MM_BLOCKSIZE environment variable. Value range: 4 - 256. Default value: 7 9.1D + -zdbo 6311 [Rollforward Utility] Allows the updates of a replication target with proutil & rfutil. 9.1D01 as of Aug, 2002 ---------------------- 9.1D01 + -ASK [Unknown] 9.1D01 + -NOREPL [Unknown] 9.1D01 + -REPL [Unknown] These changes add a latent support for site replication. 9.1D02 as of Oct 27 2002 ------------------------ 9.1D02 + -socketAddr (Removed in the next Service Packs) 9.1D03 as of Dec 4 2002 ------------------------ Solution P34002: 9.1D03 was a re-packaging of the 9.1D02 Service Pack. There are no new bug fixes. 9.1D04 as of Dec 20, 2002 ------------------------ It's a full commercial re-release for Sun Solaris 64-bit 9.1D05 as of Feb 12 2003 ------------------------ 9.1D05 + -noautoreslist [Client Session parameter] A static or dynamic query causes the SRT file to grow until all rowids are stored. When the query is closed, the space is freed. This is necessary for scolling queries, but can be avoided for non-scrolling ones. To avoid the use of the SRT file for non-scrolling queries, use the startup option -noautoreslist, or use the new query attribute FORWARD-ONLY. You will then get errors for PREV and LAST and REPOSITION etc. Also check solution P18639: How can I reduce the size of the .SRT file in Progress? 9.1D05 + -oldDebugger [Client Session parameter] With the Service Pack 5, Progress includes a new debugger for the Win32 platform, this debugger is based in Java and requires some Java components to be correctly installed and configured, if you want to use the old debugger you still can start the Progress session using the -oldDebugger parameter, this debugger does not work in UNIX. 9.1D06 as of May 16 2003 ------------------------ In order to better manage Progress SQL-92 temp table resources, Progress 9.1D06 introduced new startup parameters. Following are new startup parameters for SQL-92: -SQLCursors -SQLTempBuff -SQLTempDisk -SQLTempPgSize Solutions: P23229, What are the new SQL parameters for Progress 9.1D? P37596, Where to place the -SQLStack, -SQLStmtCache, and -SQLCursor Exchange 2003 Presentation: BP1490: OpenEdge SQL92 Performance Tips http://www.progress.com/progress/exchange/docs/powerpoints/bp1490_sql92_perf_tips.ppt RN#: 100A-10179 in V10 README.PRO Temp table startup parameters 9.1D06 -SQLCursors [SQL92 Login Broker parameter] SQL Server Max Open Cursors sets the maximum number of cursors per thread. Value range: 16 - 512. Default value: 50. Although this takes up some memory, it has very little overhead as the memory associated with the cursor information is freed when the cursor is closed or the transaction ends. Increase if -20125 error encountered. The value can be set as OPEN_CURSORS environment variable. Solution: P31698, Error 7612 and new 9.1D -SQLCursors parameter 9.1D06 -SQLStmtCache <# of statements> [SQL92 Login Broker parameter] Documentation refers it as -SQLStmtCacheSize. The number of prepared statements to be stored in SQL Statement Cache per connection. It's not shared among connections. -SQLStmtCache requires 9.1D06 or higher (solution P24543): Bug #20030108-006, the Mgr for Prepared statements has a small buffer limited to 100 prepared statements (solution P24528). Value range: 16 - 1024. Default value: 100 (statements). Large performance benefit. The overhead here is that the size of the cache grows but never shrinks. It can consume a great deal of memory depending on the statement due to it maintaining the execution tree information Update if the number of concurrent prepared statements > 100. Increase if error -210048 encountered The value can be set as CACHED_STATEMENTS environment variable. Solution: P25743, Is the limit of 1000 statements defined by CACHED_STATEMENTS P25760: How to test CACHED_STATEMENTS or -SQLStmtCache startup parameter from JDBC programs? P22575: SQL clients recieve The SQL engine Statement Manager statement cache overflowed P26935: Error 9799 when creating repeatedly more than 100 records within a Table that is having lvarbinary Datatype (Bug #20030612-003) 9.1D06 + -SQLTempBuff [SQL92 Login Broker parameter] Size of SQL Server temp table buffer (in memory cache). It replace the -SQLTempStoreBuff parameter. Value range: 100 - 200000. Default value: 1000 (KBytes). The value can be set as TPE_MM_CACHESIZE environment variable. There is 1 SQL temp table buffer for each connection to the database. The buffer holds temp table data pages in memory. The buffer is shared as needed across the sql statements in a transaction. By default, its size is 1000 1K byte units, for 10**6 bytes. As the buffer is made larger, more temp table data can remain in memory, rather than going to disk. A buffer which is too large can diminish the memory available to other server uses, or cause higher paging rates. SQL92 server uses a separate cache per each connection to the database (they are not shared among connections). Large values avoid paging to disk Increase if "no cache block" (-16003, -16005) error 9.1D06 + -SQLTempDisk [SQL92 Login Broker parameter] Size of SQL Server temp table disk storage (disk swap space). It replaces the -SQLTempStoreDisk parameter. Value range: 5000 - 100000000. Default value: 500000 (KBytes). The value can be set as TPE_MM_SWAPSIZE environment variable. There is 1 SQL temp table backing store (temp file) for each connection to the database. The backing store holds temp table data pages. There is 1 on-disk backing store page for every data page. The backing store is shared as needed across the sql statements in a transaction. By default, its size is 500000 1K byte units, for 500*10**6 bytes. This size controls the maximum total amount of data which can be sorted by a single statement. Increase if MM I/O type error (-16001) in .lg file Unused space has no runtime overhead Solutions: P23229, What are the new SQL parameters for Progress 9.1D? P33960, Certain SQL-92 queries are giving error 7631. 9.1D06 + -SQLTempPgSize [SQL92 Login Broker parameter] Replace the -SQLTempStorePageSize parameter (see above). Size in Kilobytes of a temp table data page (aka MM data block). Value range: 4 - 256. Default value: 7 (It should be 8!) The maximum recommended value is 32 (solution 21112). It's an upper limit of temp table record size) and I/O unit of cache to disk writes. Temp file located in $WRKDIR directory. A temp table data page contains an integral number of data rows. Temp table data rows cannot span pages. All temp tables have the same page size. The page size controls how big one row of data (being sorted, for example) can be. A larger page size supports sorting data with larger rows. A larger page size can also cause wasted space. Increase if sorting very large records Increase if "row too big" (-16000) error during sort The value can be set as TPE_MM_BLOCKSIZE environment variable. Solutions: P27124, Running larger SQL queries produces error (7631) on 9.1D P55344, MM Insertion error occurs with Complex SQL Query that uses Left outer join P20605, Running Update Statistics on table yields error 7721 when using high TPE_MM_BLOCKSIZE 9.1D06 + -checkwidth [0|1|2] [Client Session parameter] It allows Progress to compare the width of data in a character, decimal, or raw field with the value of the _width property for that particular field. 0 - keep the current behavior, storing beyond the _width (i.e. ignores _width value). 1 - keep the current behavior generating a warning message before storing data larger than _width. 2 - raise an error and do not store anything if data is too long. WARNING: Width of data is greater than .. (rowid ) _width. (10840) ERROR: Width of data is greater than .
. (rowid ) _width. (10841) 9.1D06 + -XMLcharesc [Client Session parameter] A new startup parameter -XMLcharesc was added to enable a user to choose the default behavior (which is to save the ' " and > characters as ' " and > respectively) when doing a DOM save, or to save these characters as the symbols themselves. 9.1D07 as of Sep 24 2003 ------------------------ 9.1D07 -checkwidth [0|1|2] [Client Session parameter] The violation of -checkwidth is recorded to a database log as well and not only to a screen. Issue #20030813-021 9.1D07 -ERO [Database Broker startup parameter] Enhanced Read-Only mode is disable outside Fathom Replication: ERO is not a supported startup argument at this time. (11170) Issue #20030528-049 9.1D07 + -combofont [Unknown] No arguments required. 9.1D07 + -mc [Client/AppServer Session parameter] Turn On Message Compression. Issue #20030903-030: need compression for appserver-client. This functionality is not available until V9.1D08 9.1D07 + -SG Number of Sort Groups [Idxbuild utility parameter] Value range: 8 through 64, default value is 48. <9.1D07 Release Notes> * The index rebuild utility allocates more memory for sorting and merging. This additional memory reduces the elapsed time required for sorting and merging key values. In this release, amount of memory required for buffers is: (number of sort groups) * (-TB) * (-TM + 1) kilobytes. * This release of the index rebuild tool requires approximately the same amount of disk space for sorting and merging as the previous version. * This release of the index rebuild tool uses more temporary files than the previous version. A set of temporary files may be opened for each sort group for each entry in the file that specifies size and location of scratch files used by index rebuild. Solutions: P43351, Progress 9.1D07 service pack provides enhanced reindex P46614, How to make idxbuild faster (starting with 9.1D07)? 9.1D07 + -tmpbsize [1|8] [Client Session parameter] Temp-table Block Size. Possible values: 1 and 8. Default value: 1. <9.1D07 Release Notes> In addition, the behaviour of the client startup parameter "-Bt" has been changed. Previously, the value specified was in kilobyte units. It is now the number of buffers, consistent with the -B database parameter. Temp-table block size used in early versions: BlkSz RPB Progress 1K 32 V8 on Unix 4K 32 V8 on Windows 8K 128 V9.0+ 1K 32 V9.1A0X (Issue #20010605-015) 8K 256 V9.1D05 (Issue #20021208-001) 1K 32 V9.1D07 with default value of -tmpbsize 8K 256 V9.1D07 with any value differed from default. Solutions: P43350, Progress 9.1D07 service pack provides enhanced performance 20339, How Parameter -Bt Works With Temp-Tables 9.1D07 + -XMLattresc [Client Session parameter] XML: decoding of attribute values XML characters ' and > are erroneously decoded when used in attribute values. 9.1D07 + -zLmc See msg 11237 [Client/AppServer Session] Compresion level used to compress messages to and from the server. Value range: 1 - 9 -zLmc 1 gives the best speed, 9 gives the best compression. The functionality behind the -Z*mc parameters is not available until V9.1D08 9.1D07 + -zMmc See msg 11236 [Client/AppServer Session] The value in kilobytes identifing the size of the buffer used to compress messages to and from the server. Value range: 8 - 32 9.1D07 + -zMminmc See msg 11238 [Client/AppServer Session] The minimum size for an uncompresed message before it is considered for compression. Value range: 0 - 32,000 9.1D08 as of Jan 20 2004 ------------------------ 9.1D08 -mc [Client/AppServer Session parameter] Turn On Message Compression. Also see the -zMmc, -zLmc, -zMinmc parameters. Issue #20030903-030: need compression for appserver-clien Message Compression (20040116-003) The message compression startup switch, "-mc", should be set only for Progress clients talking to compatible servers. Use the "-mc" startup switch between Progress 9.1D08 clients and Progress 9.1D08 AppServers. 9.1D08 clients to other versioned servers and viceversa are also unsupported. Attempting to exercise compression between incompatible client\server combinations will result in communication errors which will be resolved in subsequent patches to both versions. Regardless, it is important to remember that compression will be disabled when clients that turn on compression connect to AppServers that do not have this capability. 9.1D08 + -glbshvarfix [Compiler Session parameter] Bug# 20030924-031 deals with the fact that if a procedure has global shared variables with initial values, the compiled r-code for that procedure is not fully portable between OS platforms. This was fixed on both OE10 and 9.1D08, but as it required a change in r-code format. Because of this, 9.1D08 contains the -glbshvarfix parameter to explicitely activate the fix -it must be specified for the compiler session for the bug fix to take effect- to safeguard the rcode compatibility with earlier service pack levels. 9.1D08 + -noincrwarn [Client/AppServer Session parameter] Suppress warning messages (5407),(5408),(5409),(5410): WARNING: [-nb|-l|-mmax|-D] exceeded. Automatically increasing from to . (54XX) KB-P79795: How to suppress warning messages (5407),(5408),(5409),(5410) from displaying on client screens. From 9.1D08 onward. 9.1D09 as of May 26 2004 ------------------------ 9.1D09 -sbhelp Spacebar Help [Unknown] When you are in a blocked state with a "press spacebar to continue" message on the screen, the "help" key can be used to call the specified function. 9.1E as of Nov 2004 --------------------- 9.1E + -varviewas (9.1E only) [Unknown] 9.1E + -zsigdb (9.1E only) [Any processes] Turn on signal handling messages: fdsig, prosig, drSigclient KB-P91057: What is -zsigdb ? Starting on 9.1E a new startup option -zsigdb is being introduced to allow additional debugging messages to be written in the database log file when debugging specific issues related to signal handling. The messages created will indicate when a process, such as _mprshut, is sending a signal to disconnect a client, or when a process receives a signal from another process or the operating system. This option can be used for any _progres, _mprosrv, _proutil, etc process that you want to see signal debug messages for. 9.1E01 as of Feb 2005 --------------------- 9.1E01 + -normtshutdown [Database Broker startup parameter] No remote shutdown Sarbanes-Oxley Security Requirement Service Pack 9.1E01 adds a new startup parameter that causes the database broker to disallow remote database shutdown requests. A recent Sarbanes-Oxley audit at a customer site uncovered this issue. In anticipation of more customers needing to address this same issue, Service Pack 9.1E01 delivers the ability to automatically all deny remote shutdown requests. The error message below is displayed and the shutdown request is denied. "Shutdown request denied because you are an invalid user, remote shutdown is not allowed, or the database is enabled for Failover Clusters, (12566)" If the remote shutdown request is made from an older version of Progress the shutdown request is denied, but a different error message is displayed: "Shutdown request denied; you do not have the correct user ID. (547)" -Bp with online backup Issue #20041203-030 Richard T. Banville wrote: The statements in the reply here are correct but just to clarify a bit: The fix was two fold. 1) do not LRU blocks read into the -B buffer pool from disk for online backup (blocks already in the buffer pool were never moved to the LRU end) This avoids fouling the LRU mechanism of the -B buffer pool but has the "possibility" of increasing contention at the LRU end of the buffer pool (A traffic jam of sorts at the LRU end of the -B buffer chain can occur when the buffer hit ratio is low for other users on the system - this occurs when other users do lots of page ins as a normal part of their application - also something to be avoided for performance reasons but that's another discussion) 2) honor -Bp to mitigate any possible performance issue with solution to #1 (may or may not be needed but is the best way to go if not sure) 9.1E02 as of Aug 2005 --------------------- 9.1E02 + -noqryorderadd [DataServer for ORACLE] 9.1E02 + -noqryuniqueadd [DataServer for ORACLE] All queries with a USE-INDEX or BY clause provide sort criteria to an Oracle query RN#: 101A-00233 =============== All queries with a USE-INDEX or BY clause provide sort criteria to an Oracle query. But, in the absence of such clauses, the Progress 4GL may choose its own index to satisfy the query request. In order to avoid Progress index selection on queries that are not explicit about sorting, new startup and query-tuning options have been added to bypass Progress index selection. If the -noqryorderadd startup option is set, all queries in the Progress session that would have responded to the Progress selected index will no longer specify sort criteria to the Oracle query. Enabling the server to control the order of records returned may yield a performance benefit in certain database configurations. To bypass the Progress index selection of a specific query, the NO-QUERY-ORDER-ADDED QUERY-TUNING option has been added to the query statement. Along with index selection, the 4GL may also determine that a unique index is required for scrolling purposes within the DataServer. If the selected index is non-unique but needs to be made unique for scrolling purposes, the OracleDataServer may add uniqueness to the ORDER BY clause of the Oracle query. Since the derived unique order may not correspond to a real index on the server, there may be performance ramifications to using the derived order. Therefore, to bypass the unique order adjustment at the session level, the -noqryuniqueadd startup option has been added. The NO-QUERY-UNIQUE-ADDED QUERY-TUNING option bypasses unique ordering at the query level. IMPORTANT NOTE: Turning off unique ordering in cases where scrolling is required by the 4GL may result in behavior incompatible with Progress. This option should only be used for the sake of performance in cases where scrolling over the query results is not required by the 4GL. Progress DB to ORACLE Conversion dialog box and Generate Delta SQL utility dialog box each support Use Shadow Columns 10.0A as of Dec 13 2003 ----------------------- 10.0A -cpinternal/-cpstream These parameter now support Unicode for interactive GUI clients (Unicode GUI clients) V9.1D/3.1D Webspeed supports Unicode In version 9.1B, Progress supports Unicode as an internal code page in the Batch Client, Application Server, SQL-92 Server, and Database Server. Unicode is not supported in WebSpeed agents, GUI and Character Clients, and Dataservers. 10.0A -logentrytypes [Client Session parameter] A character string that specifies a comma-separated list of log entry types. By default, the logging level you specify using the Logging Level (-logginglevel) startup parameter applies to all log entry types specified. However, you can specify a different logging level for each entry type, as follows: log-entry-type[:level] A logging level has value between 0 and 4. The value can be change using LOG-MANAGER:LOG-ENTRY-TYPES. 10.0A + -Binding [Web Service connection parameter] Local name of the binding element contained in the WSDL document. Used in conjunction with SoapEndpoint. This parameter is optional if the WSDL contains only one binding. If -Binding is specified in the SERVER:CONNECT connect-options string, -SOAPEndPoint must also be specified. If -Service and/or -Port are specified in the SERVER:CONNECT connect-options string, neither -Binding nor -SOAPEndpoint is valid. 10.0A + -BindingNamespace [Web Service connection parameter] The namespace of the binding element within the WSDL document that the application will use. This optional field is needed only if the local binding-name is not unique. 10.0A + -debugReady [0 | port-number] [Client Session parameter] The port on which Progress opens a socket for connecting to the attachable Debugger. The AppServer does not currently support the attachable Debugger. -debugReady will be ignored. (11818) You specified -debugReady for an AppServer process to make it ready to be attached to by the Debugger. This is not supported. You cannot specify -debug and -debugReady at the same time. (11819) These two parameters are incompatible. If you bring up Progress with -debug and also want to make it ready to be attached to you should use the proDebugConfig tool. 10.0A + -IB [idxbuild] KB-P110110: Index rebuild fails with an error message Dbkey is not the first dbkey on free Chain Run the idxbuild again, now with -IB 0 parameter, which will use old (non-optimized) algorithm for sorting. 10.0A + -connectionLifetime [AppServer session model connection] The maximum number of seconds that a given connection can be used before it is destroyed. Connections whose lifetime exceeds the specified value are destroyed as they become available. Default value: 300. An available connection is one that is not currently reserved to run a request. Bound connections associated with remote persistent procedures are not available for re-use until the persistent procedure is deleted. So, bound connections remain available as long as necessary, even if they exceed the specified value. 10.0A + -initialConnections [AppServer session model connect] The number of connections established when the CONNECT() method executes on a given server handle. If the specified number of connections cannot be created, the CONNECT() method fails and any successfully-created connections are closed. Values should be great than zero. Default value: 1. 10.0A + -maxConnections [Web Service connection param] hWS:CONNECT("-WSDL -maxConnections 50"). Maximum number of connections maintained between the client and the Web Server for asynchronous requests. If num connections is less than or equal to 0, the application is requesting no predefined limit on the number of connections. If the client application exceeds the specified number of connections, the asynchronous requests are queued. 10.0A + -minConnections [Web Service connection parameter] 10.0A + -nsClientDelay [AppServer session model connection] The interval, in milliseconds, that the client waits between attempts to get a valid UDP port number when attempting to communicate with the NameServer. Default value: 0. 10.0A + -nsClientMaxPort [AppServer session model connection] The maximum value for the UDP port number used by the client when communicating with the NameServer. If this value is zero, OpenEdge chooses the NameServer client port randomly. Default value: 0. 10.0A + -nsClientMinPort [AppServer session model connection] The minimum value for the UDP port number used by the client when communicating with the NameServer. If this value is zero, OpenEdge chooses the NameServer client port randomly. Default value: 0. 10.0A + -nsClientPicklistExpiration [AppServer session model] The maximum amount of time, in seconds, that the client retains an AppServer pick list for an application service. Default value: 300. 10.0A + -nsClientPicklistSize [AppServer session model connection] The number of AppServer picks to request from the NameServer each time it looks up the available AppServer connections for a given application service name. Default value: 1 10.0A + -nsClientRetry [AppServer session model connection] 10.0A + -numlogfiles [Client Session parameter] The number of log files to keep. You also can use the NUM-LOG-FILES attribute on the LOG-MANAGER system handle. Value range: 0, 2 or greater. 0 means there is no limit on the number of log files to keep. Default value: 3. 10.0A + -Port [Web Service connection parameter] The local name of the port element contained within the service element. Used in conjunction with -Service. This parameter is optional if -Service contains only one port. 10.0A + -Service [Web Service connection parameter] The local name of the service element within the WSDL document that the application will use. This field is optional. Many WSDL documents only support one service and this parameter is optional if there is only one (or zero) service elements defined. Used in conjunction with -Port. 10.0A + -ServiceNamespace [Web Service connection] The namespace of the service element within the WSDL document that the application will use. Most WSDL documents only support one service and this parameter is optional if there is only one service defined. This parameter is used in conjunction with -Service and is ignored if -Service was not specified. This parameter is optional if namespace is included in -Service. 10.0A + -SOAPEndpoint [Web Service connection parameter] The URL identifying the endpoint for this Web Service. Used in conjunction with Binding. It is an error to use this parameter in conjunction with -Service or -Port. 10.0A + -SOAPEndpointUserid [Web Service connection parameter] Optional user account name to use to connect to a Web Service that hosts the Web Server application. If -SOAPEndpointUserId is specified and -SOAPEndpointPassword is not, OpenEdge uses a blank password. 10.0A + -SOAPEndpointPassword [Web Service connection parameter] Optional password to use with the -SoapEndpointUserId. This attribute is ignored if -SoapEndpointUserId is not specified. 10.0A + -TargetNamespace [Web Service connection param] The namespace contained in the WSDL document. This parameter can be used as a version check. The information in this parameter is compared against the -TargetNamespace contained in the WSDL document. If they do NOT match the CONNECT() method fails. 10.0A + -WSDL [Web Service connection parameter] The location of the WSDL document. This required parameter is the URL specified location of the WSDL document. The document can be local or remote. The location can optionally contain a users account name and password to use when connecting to the Web Server. If the protocol is not part of the wsdl-document's URL, the 'file' protocol is assumed. Additionally, the 'file' can be a relative pathname as it is relative to the current-working directory. The -WSDL parameter must be specified when connecting to a Web Service 10.0A + -WSDLUserid [Web Service connection parameter] Optional user account name to use to connect to a Web Service that hosts the WSDL document. If -WSDLUserId is specified and -WSDLPassword is not, OpenEdge uses a blank password. 10.0A + -WSDLPassword [Web Service connection parameter] Optional password to use with the -WSDLUserId. This attribute is ignored if -WSDLUserId is not specified. 10.0A + -xbsa [Backup Services API ?] 10.0A + -xbsahost [Backup Services API ?] 10.0A + -xbsapolicy [Backup Services API ?] 10.0A + -xbsaschedule [Backup Services API ?] 10.0B as of Aug 5 2004 ----------------------- 10.0B + -REPLTargetCreation [Online Utility parameter] proquiet sourcedb enable -ReplTargetCreation probkup online source source_bak -REPLTargetCreation KB-P92539: Fathom High Availability Replication 10.0B Specify the -REPLTargetCreation parameter anytime an online backup or a proquiet is performed against a Replication Source database. 10.0B + -certstorepath [Unknown] 10.0B + -keyalias [Database Server parameter] Specifies the alias name of the Secure Sockets Layer (SSL) private key/digital certificate key-store entry to use. Use Key Alias (-keyalias) to identify a SSL private key/digital certificate key-store other than the default. 10.0B + -keyaliaspasswd [Database Server parameter] Specifies the encrypted Secure Sockets Layer (SSL) Key Alias Password to use to access the server’s private key/digital certificate key-store entry. The default is "password". Use Key Alias Password (-keyaliaspasswd) to allow access to the Key Alias when you use a Key Alias other than the default. The key-alias-password value must be encrypted. You can use the genpassword utility, located in your installation’s bin directory, to encrypt the password. 10.0B + -keystorepasswd [Unknown] 10.0B + -keystorepath [Unknown] 10.0B + -nosessioncache [Login Broker parameter] Use No Session Cache (-nosessioncache) to disable SSL session caching. Session caching allows a client to reuse a previously established session if it reconnects prior to the session cache timeout expiring. Use No Session Cache (-nosessioncache) to disable this feature. Session caching is enabled by default. 10.0B + -nosessionreuse [Client Session parameter] Use No Session Reuse (-nosessionreuse) when you do not want to reuse a Secure Sockets Layer (SSL) session ID to reconnect to the same SSL-enabled database server. 10.0B + -sessionModel [AppServer Connection parameter] This property must be set for session-free application. It is optional for session-managed applications. The value for the -sessionModel parameter is case-sensitive. (KB-P40074) Possible values: Session-managed Session-free Example: :CONNECT("-sessionModel Session-free......."). 10.0B + -sessiontimeout [Login Broker startup parameter] Specifies in seconds the length of time a SSL session will be held in the SSL session cache. The default is 180 seconds. Use Session Timeout (-sessiontimeout) to change the length of time that a SSL session will be cached. SSL session caching allows a client to reuse a previously established SSL session if it reconnects prior to the SSL session cache timeout expiring. 10.0B + -ssl [Client/Login Broker parameter] Use SSL-based Connection (-ssl) to specify a Secure Sockets Layer (SSL) connection to all database and client connections for data privacy. SSL provides an authenticated and encrypted peer-to-peer TCP connection. Note: Be sure you need SSL before using this parameter. SSL incurs more or less heavy performance penalties, depending on resources and load. This parameter applies to ALL database connections from current client session (KB-P85399). Example: proserve -S -ssl 10.0B + -sslalgorithms [Unknown] 10.0B01 as of Dec 2004 ---------------------- 10.0B01 + -ttmarshal [Client and Appserver Startup option] In order to reduce network traffic for temp-table schemas passing between clients and Appservers, we are introducing a new startup option, -ttmarshal, and a new SCHEMA-MARSHAL property for temp-tables. This new startup option is for the client, appserver, webspeed and any other 4gl-capable executable. -ttmarshal n where n is a number from 0 to 4 meaning: 0 -- ignore this option 1 -- min-schema-marshal for static temp-tables 2 -- min-schema-marshal for all temp-tables 3 -- no-schema-marshal for static temp-tables 4 -- no-schema-marshal for all temp-tables If you specify a non-zero value for this option, the normal full marshalling for temp-tables will be suppressed and less data will be marshaled according to the value given. If any particular table has the SCHEMA-MARSHAL property (or NO-SCHEMA-MARSHAL or MIN-SCHEMA-MARSHAL) explicitly set, then the table property overrides the session startup option. No-schema-marshal means that no field or index information is sent over the network. This is legal only if the receiving side is static, or is dynamic with a pre-existing temp-table definition. If the receiving table is dynamic with an unknown temp-table definition, then an error will result. In addition, no error checking is possible in these cases, since no field information is sent to allow it, so the user must be very certain that the two tables, receiving and sending, match. Min-schema-marshal never produces errors and is legal in all configurations. But since it sends labels, formats, help messages and validation expressions as UNKNOWN, it can cause the appearance of a dynamic unknown receiving table to be missing these things. If the receiving table already has a definition, it will make no difference at all. There will also be complete error-checking, since the field names, datatypes and extents are sent. KB-P104926: How to set session wide TEMP-TABLE Schema marshaling attributes? 10.0B02 as of Apr 2005 ---------------------- 10.0B02 + -noincrwarn [Client/AppServer Session parameter] See in 9.1D08 -Bp with online backup See in 9.1E01 10.0B03 as of Sep 2005 ---------------------- 10.0B03 + -noudfinwhere [Compile-Time parameter] Issue #20030404-003 Use No UDF in WHERE Clause (-noudfinwhere) to restrict the invocation of user-defined functions and methods from within WHERE clauses. When specified, invoking a user-defined function or method from within a WHERE clause generates a compiler error. If -noudfinwhere given you may not have user-defined-functions or methods in a WHERE clause. (12742) The -noudfinwhere is provided to alert programmers to the dangers of having user-defined-functions and methods in a WHERE clause. They may obscure error conditions in the WHERE clause. They can be safely executed in a separate statement before the statement with the WHERE clause, since as elements of a WHERE they are never executed repeatedly during a FOR EACH block, but rather are executed only once before the FOR EACH starts. So it is equivalent to evaluate them to a variable outside the FOR EACH or FIND and then use that variable within the WHERE clause. 10.1A as of Dec 20, 2005 -------------------- 10.1A + -aiarcdir [Extent Management daemon] Specify the directories where the AI File Management utility writes the archived after-image files. When the After-image Extent Management is enabled for a database, the AI Extent Management daemon process is automatically started by the database broker during startup. The -aiarcdir argument is required to successfully start the daemon. 10.1A + -aiarcdircreate [Extent Management daemon] Direct the AI File Management utility to create the specified directories. 10.1A + -aiarcinterval [Extent Management daemon] Specify on-demand mode archiving or the extent switch interval for timed-mode archiving. Specify 0 for on-demand mode. For timed-mode, the minimum value is 120. 10.1A + -checkseal [proutil -C auditarchive] Specifies that AUDITARCHIVE verify that the seal of each audit data record matches the database MAC key prior to writing it to the audit archive file. This option requires that the audit policies in effect when writing the audit data records have specified a Data Security Level of DB Passkey. For more information on creating audit policies and data security, see OpenEdge Getting Started: Core Business Services. 10.1A + -clearlog [Client Session startup parameter] Use Clear Log (-clearlog) to delete any file that matches the name of specified client log file identified by Client Logging (-clientlog) parameter. 10.1A + -clred [Unknown] 10.1A + -dataset100 [Compile-Time Parameter] Use DataSet100 (-dataset100) when you have r-code containing ProDataSet objects that you want to compile in OpenEdge 10.1, and run in both OpenEdge 10.1 and 10.0. This startup parameter directs Progress to compile references to ProDataSet objects in an OpenEdge 10.0 manner, which results in r-code that will run in both 10.1 and 10.0 environments without error (providing you have not used any new OpenEdge 10.1 features). You may not have REFERENCE-ONLY datasets with -dataset100. (12717) If using startup option -dataset100, all .p's being compiled must contain only pre-version 10.1a elements, since the purpose of it is to produce r-code that can be executed by version 10.0b. 10.1A + -DirBlock [Unknown] 10.1A + -directory [proutil -C auditarchive] Specifies the directory where the audit archive file is written. If you do not specify a value for directory-name, the file is written to your current working directory. If an audit data archive file for your database already exists in the output directory, you are prompted to confirm if you wish to proceed and overwrite the existing file, or exit the utility. If you are purging your audit data and do not want the data written to the archive file, you must explicitly specify the “bit bucket” (/dev/null) as the output destination in directory-name. 10.1A + -domain [Fathom Management] Management domain. Default Fathom1. 10.1A + -dumplist [Binary Dump Utility] Points a file with a list of the dump files generated. For a threaded dump, create a file, dumpfile, that lists all the files created by the binary dump. dumpfile can be used as an input parameter to binary load. 10.1A + -ide Using the IDE debugger RN#: 101A-00054 When configured to use the IDE debugger using the -ide parameter, then the traditional Debugger will not be able to launch, for example, from the Progress Help Dialog. 10.1A + -newinstance [Unknown] 10.1A + -nodelete [proutil -C auditarchive] Specifies that AUDITARCHIVE copy the audit data records to the archive file, leaving the audit data in the database. If not specified, AUDITARCHIVE will delete the audit data records as they are archived. 10.1A + -nosavepoint [Client Sessions] KB-P114934: Transaction backout taking long time on 10.1A, application has many nested blocks with ON ERROR UNDO When a 4GL clients undoes a transaction, it must do the same operations carried out during forward processing, but with an inverted sign: if a record was created during forward processing, it must be deleted during transaction backout. Therefore, transaction backout generates some new database activity; for crash recovery to work correctly, this new database activity must be recorded in the before-image file as well, just as it happens with forward processing. When undoing a transaction, a client will end up writing twice as many before-image notes as with forward processing. Before the introduction of savepoints in 10.1A, the undoing of a subtransaction was handled and optimized via the local before-image file, which led to the net result that only just about as many notes would be written during transaction rollback as they were written during forward processing. FIX: Use the -nosavepoint startup option on your client processes [_progres, _proapsv, prowin32, etc]. This option restores the pre-10.1A local before-image mechanism. 10.1A + -password [Fathom Management] Password associated with the -user username specified. Note: Use of the -password parameter might allow others to see your password in readable clear text. 10.1A + -preferidx [Unknown] 10.1A + -recs [proutil -C auditarchive ] Specifies the number of records to delete in a single transaction. AUDITARCHIVE executes a transaction for every num-recs records it deletes. The default for num-recs is 100, and the maximum is your current Lock Table Entries (-L) setting. The multi-user default for -L is 8192. 10.1A + -REPLTransition [Prorest utility] prorest db-name backupsource -REPLTransition Using the database restore utility with the -REPLTransition parameter, you can transition a source database to a target database. When the restore utility transitions a database, it performs a subset of the offline transition processing. 10.1A + -rowidNoSchemaMatch [Unknown] 10.1A + -showppuerr [Client Session startup parameter] Use Show PPU Error (-showppuerr) to restore the warning for message 4132 (“Invalid character unit value . Changed to 320.”). Progress raises a warning message 4132 when a 4GL program attempts to set a column or width attribute to a value greater than 320. Progress resets the column or width attribute value to 320 and suppresses the associated warning message. KB-P12469: Expanded/Virtual Screen Resolutions and Progress Limits Starting with OpenEdge 10.1A, steps have been taken to alleviate the issues caused by this limit: - The error 4132 is now suppressed by default, and will only be shown if the startup parameter -showppuerr was provided for the session. - Any PPU based assignment that exceeds the limit will be forced to 320. - Note that the limit itself still exists. Session:width-pixels divided by Session:pixels-per-column must be less than 320 in order to avoid error (4132). 10.1A + -SMQPID [Unknown] 10.1A + -SMQPort [Unknown] 10.1A + -SQLTempMgr [Unknown] 10.1A + -thread [0|1] [Binary D&L and Index rebuild] -threads 0 directs the index rebuild to execute in an unthreaded mode. -thread 1 indicates a multi-threaded. 10.1A + -threadnum [Binary D&L and Index rebuild] For Enterprise database licenses, index rebuild is multi-threaded by default. You can specify the maximum number of threads created using the -threadnum n parameter. If not specified, the maximum number of threads created will equal the system’s number of CPUs. The actual number of threads created will not exceed the number of index groups in an area if this value is smaller than the maximum. During a multi-threaded index rebuild, separate threads are assigned the external merging of each index group during Phase 2. Once the main process has created all the threads for Phase 2, it immediately begins building the index tree for Phase 3, enabling Phase 3 to be executed in parallel with Phase 2. If an area has only one index to rebuild, the work will be executed without the use of threads. 10.1A + -ucc Unicode Character Client [Unknown] Mentioned in the issue #20060522-008 using -ucc with QAD, char fields seems to byte count and not column count Fixed in 10.1A02 10.1A + -ufillin [Unknown] 10.1A + -ulayout [Compile-Time parameter] The -ulayout parameter takes an argument that must be between 0 and 16, inclusive. This argument indicates how many bytes per column to reserve for a string in the text segment. 10.1A + -user [Fathom Management] Username on machine where the AdminServer resides. Default is current user. Not needed for local connection. 10.1A + -userid [proutil -C auditarchive] Specifies the user name of the user privileged to execute the archive. If you are using the _User table, username must be defined there, and you must include the -userid parameter to identify the user. If you are not using the _User table, use of -userid is optional; in this scenario, username specifies a local operating system login ID. Regardless of the source, username must have the Audit Data Archiver privilege in order to execute AUDITARCHIVE. 10.1A + -usewidgetid [Client Session startup parameter] Use the Use Widget ID (-usewidgetid) startup parameter to enable application-defined widget IDs for Progress widgets defined in your OpenEdge GUI application. Specifying application-defined widget IDs for Progress widgets defined in your OpenEdge GUI application allows you to identify those widgets at runtime while testing your application with a third-party automated test tool. When specified, Progress uses any application-defined widget IDs when creating the widgets at runtime, instead of using the widget IDs it normally generates by default. The widget ID value of any given widget remains the same across OpenEdge sessions, unless you purposely change the value using the WIDGET-ID attribute for that widget. This allows a third-party automated test tool to identify the same widget consistently each time you run the tool with your application. 10.1A02 as of Oct 2006 ---------------------- 10.1A02 + -icucistr [Unknown] 10.1A02 + -icucsstr [Unknown] They seem to relate ICU (International Components for Unicode) library 10.1A02 + -noxrefvals [Unknown] READMESP.txt 2. Changes to XREF ------------------------------ The XREF option on the COMPILE statement generates a listing of cross-reference information between procedures and classes, and the objects referenced in them. This option will be more fully supported in 10.1A01 for classes in that more detailed information will be available for references to OO4GL features. The -noxrefvals might be related the one of the follwing issues: Issue #20060609-014 Some entries for private temp-table and dataset fields appear in XREF output when they should not Fixed in 10.1A02 Issue #20050217-005 Implicitly converted strings (such as the ones generated for the LIST-ITEMS and LIST-ITEM-PAIRS phrases when the items are integers) are listed in the string XREF file. Fixed in 10.1A01 Issue #20051018-040 No entries are being produced for CLASS information when compiling with XREF Fixed in 10.1A01 10.1A02 + -scrvalmode [1|3] Screen-value Mode KB-P98127: SCREEN-VALUE of an empty value in a COMBO-BOX returns different results in Progress 9.1x and OpenEdge Screen-value Mode (-scrvalmode) Use Screen-value Mode (-scrvalmode) to specify the mode in which the SCREEN-VALUE attribute indicates that the selected item in a combo-box item list is empty. The screen-value mode. Valid modes are: * 1 — If the selected item in the combo-box list is empty, the SCREEN-VALUE attribute for the combo-box returns the empty string (""). Note that if no item in the combo-box list is selected, the SCREEN-VALUE attribute returns the Unknown value (?). In either case, the INPUT-VALUE attribute returns the empty string (""). * 3 — The same as mode 1, with the following exception: if the SCREEN-VALUE attribute for the combo-box returns the Unknown value (?), the INPUT-VALUE attribute also returns the Unknown value (?). In Release 9.1, the SCREEN-VALUE attribute for a combo-box returns the empty string ("") if the selected item in the list is empty. Starting with Release 10.0, the SCREEN-VALUE attribute for a combo-box returns the Unknown value (?) if the selected item in the list is empty. In either case, if no item in the combo-box list is selected, the SCREEN-VALUE attribute returns the Unknown value (?). This startup parameter does not apply to combo-box browse columns. Also read READMESP.txt 10.1B as of Jan 10 2007 ----------------------- 10.1B + -keybuildtype [Unknown] 10.1B + -lkrela Use the alternate lock release algorithm: restore pre-V10.1B behaviour. Use only if you get the error 13910: SYSTEM ERROR: Calling oldLktend to remove locks. Consider using -lkrela database startup parameter to use the alternate lock release algorithm. (13910) Richard T. Banville wrote: http://www.peg.com/lists/dba/web/msg24184.html 10.1B released a feature where record locks are maintained in per user lists. In previous releases, when a transaction ended or when a user logged out, the entire lock table was scanned to ensure that all appropriate locks have been release (I say appropriate because locks can be held outside a transaction but not outside of a connection). With very large lock tables becoming more common, the scanning of the entire lock table can cause noticeably contention with other transactions running on the system. This new feature avoids the scanning of the entire lock table while maintaining the lock checking functionality. It improves logout, transaction end and concurrent lock table processing. The message refers to a switch that allows the old behavior of scanning the entire lock table to be executed. I thought there was a release note associated with this switch. In any event, it is not suggested that you run with this switch unless you are seeing this error message which indicates a bug in the new algorithm. Old version of KB-20616: Does a large -L value have any impact on system performance? But both connecting and disconnecting from the database causes the client to perform a front to back scan of the entire lock table. The larger -L is set, the more CPU time is assoiciated with these 2 operations. Gus Bjorklund wrote: http://www.peg.com/lists/dba/history/200102/msg00563.html We do it as an internal sanity check - bad things happen if a previous connection happens to somehow disconnect without removing all of its locks. There were bugs in the past where locks were left behind after their owner no longer existed. We put the checks in so if new bugs causing abandoned locks should appear, we would know about them. 10.1B + -maxAreas Specify the highest area number available for use during the time the database is online. Maximum and default value: 32000 (though msg 13639 says: "The default is 1000. The maximum is 32767.") The memory "cost" is less than 290 bytes per entry. 10.1B + -noint64 Use No INT64 to execute Release 10.1B code with Release 10.1A executables. If you specify the -noint64 startup parameter: * The functions that are compiled as INT64 in Release 10.1B (CURRENT-VALUE, DYNAMIC-CURRENT-VALUE, DYNAMIC-NEXT-VALUE, ETIME, GET-POINTER-VALUE, GET-SIZE, INTERVAL, NEXT-VALUE, and SEEK) are compiled as INTEGER. * INT64 constants are compiled as DECIMAL. * ABL source code references to INT64 variables and fields generate errors. * Code that subtracts two DATETIMEs generates a compile-time error. * The XML schema long data type (64-bit signed integer) maps to the ABL DECIMAL data type rather than the INT64 data type. This mapping applies to: – The bprowsdldoc and bproxsdto4gl command line utilities. – The Web Services Client runtime product. 10.1B + -nominfix [Unknown] 10.1B + -shmsegsize [G] Shared memory segment size Use Shared memory segment size (-shmsegsize) to specify the size of the largest shared memory segment the server can allocate. Minimum and default value: 128 for 32-bit systems, 1024 for 64-bit systems. Unit: - MB, G - GB Specifying shared memory segment size can improve performance. Increasing the size of the shared memory segments decreases the number of segments allocated, in turn decreasing the system resources needed to manage the segments. If the value is measured in giga-bytes (GB) then must be 1, 2, 4, 8, 16, or 32 (Msg 13740) 10.1B -B Number of Database Buffers. Max value is increased: The maximum value for -B is 125,000,000 for 32-bit platforms and 1,000,000,000 for 64-bit platforms, but in practice, you will never set -B that high. The maximum amount of shared memory that can be allocated is operating system dependent and will never exceed the following maximums: * Approximately 4GB on 32-bit systems. * Approximately 8TB on 64-bit systems. The maximum shared memory segment size is: * Approximately 4GB on 32-bit systems. * Approximately 32 GB on 64-bit systems. The maximum number of shared memory segments is: * 32 on 32-bit systems. * 256 on 64-bit systems. Gus Bjorklund wrote: http://www.peg.com/lists/dba/web/msg24197.html 32-bit programs have a /total/ address space of 4 GB. But that is for everything: os kernel needs some, code, stacks, heap, shared libraries, file buffers, memory mapped files, etc. etc. all in addition to the shared memory segments used by the database. So 32-bit 10.1B /cannot/ address 4 GB of shared memory on any operating system. 10.1B includes a feature that allows adjustment of the maximum shared segment size that the database will ask the operating system for (it was fixed at 128 MB in earlier (v9, 10.0, 10.1A) releases). That feature allows you to set the /requested/ segment size larger, but the operating system is still going to impose its limits on the size and number of segments. So in practice, on 32-bit versions, you will still be limited to a total of somewhere in the neighborhood of 2 gigabytes of shared memory segments. The actual limit will vary by operating system, kernel configuration parameter settings, and the application itself. On Linux youcan get about 2.7 GB of shared memory. Other operating systems have lower limits. 10.1B + -TXESkipLimit TXE Commit lock skip limit (msg 13896) KB-P121754: How to change the Commit Lock Skip Limit for the TXE in promon? http://progress.atgnow.com/esprogress/Group.jsp?bgroup=progress&id=P121754 In 9.1E03, 10.0B03 and later, the TXE algorithm was changed in an effort to ensure that TXE Commit Locks will not be starved. The new algorithm provides for 10,000 TXE Share and TXE Update Lock Requests to be processed prior to the TXE Commit Lock Requests. The goal is to have this new algorithm auto or self tuned in the future. Currently this new algorithm can be manually tuned via promon depending upon the contention being experienced. KB-P101215: Poor performance on high powered UNIX machines - bottlenecking on the TXE http://progress.atgnow.com/esprogress/Group.jsp?bgroup=progress&id=P101215 A new parameter was introduced to tune the TXE locking behavior. We don't usually recommend customers to change its value, but if they do want to, they can tune the parameter in the following way: promon dbname Enter the following commands: R&D debghb 6 10 3 The window is called "Adjust TXE Options", the option to tune this paramter is option 3: "TXE commit lock skip limit". The default value is set to 10000. This value can be changed under the following circumstances: 1. Set it to 0 (zero) will restore to the old TXE locking algorithm. 2. Usually increasing the value will get better performance. However, if the customer notices very long COMMIT or UPDATE locks queued (from the promon "Activity: TXE Lock Activity" window), and also the system performance slows down, then this value should be decreased. 3. The new algorithm gives Record Delete Operation lower priority. If customer wants to increase the priority for this kind of operations, the value should be decreased or even set to 0. Notice that this parameter sets the maximum SHARE/UPDATE locks that can skip the queued COMMIT locks. If it has to be changed, do it in a rather large scale. For example, by changing it from 10000 to 10001 should not make any difference. 10.1B01 as of Apr 2007 ---------------------- 10.1B01 + -disabledeltrig [Unknown] Maybe related to the issue Number: OE00067909 DELETE trigger not disabled with ALLOW-REPLICATION DISABLE TRIGGERS using the ALLOW-REPLICATION clause was disabling only CREATE, ASSIGN, and WRITE triggers, and not DELETE triggers. or to KB-P96152: Cannot suppress error 11914 when using SAVE-ROW-CHANGES() to delete a record http://progress.atgnow.com/esprogress/Group.jsp?bgroup=progress&id=P96152 ProDataSet Using SAVE-ROW-CHANGES() method of Buffer object handle to delete a record If the delete operation fails, for example the database delete trigger returns an error, the following error message is displayed: Unable to delete record in the database during SAVE-ROW-CHANGES. (11914) Using SAVE-ROW-CHANGES() with NO-ERROR option doesn't suppress the error message CAUSE: Bug# 20041012-004 FIX: Upgrade to 10.0B01 or later release KB-P93163: DISABLE TRIGGERS documentation is wrong http://progress.atgnow.com/esprogress/Group.jsp?bgroup=progress&id=P93163 Documentation doesn't explicitly states that DISABLE TRIGGERS FOR LOAD will disable also replication related trigger and DELETE trigger. Disabling triggers for LOAD disables all triggers associated with the CREATE, WRITE, DELETE, REPLICATION-CREATE, REPLICATION-WRITE, REPLICATION-DELETE, and ASSIGN events for the named table. 10.1B02 as of Aug 3, 2007 ------------------------- + -align Fix a Linux alignment problem in OpenEdge 10.1B between 32-bit and 64-bit OpenEdge versions of probkup. + -AreaCheck Area block consistency check Enables a consistency check that will be applied to all index blocks and record blocks (except BLOB blocks) in the specified area. + -DbCheck Database block consistency check Enables a consistency check that will be applied to all index blocks and record blocks (except BLOB blocks) in the entire database + -IndexCheck Index block consistency check Enables a consistency check that will be applied to all index blocks of the specified index. This check is for index blocks only. + -MemCheck Memory overwrite check Enables memory overwrite checking at runtime and during roll forward + -TableCheck Record block consistency check Enables a consistency check that will be applied to all record blocks (except BLOB blocks) of the specified table. This check is for record blocks only. Promon > R&D > 4. Administrative Functions > 8. Enable/Disable block level consistency check Current consistency check status: 1. -MemCheck: disabled 2. -DbCheck: disabled 3. -AreaCheck: disabled 4. -IndexCheck: disabled 5. -TableCheck: disabled + -recspacesearchdepth Record Free Chain Search Depth Factor Determines how deep in the Record Free Chain to search, to find a block with enough free space to fit data, before allocating a new clusters worth of space instead from the Empty Chain where the Area High Water Mark (HWM) is raised. Old algorithm: No more than 3 blocks at a time will be examined and moved to the tail end. -Bp allows an online backup to make use of (-Bp) Private Read-Only Buffers. 10.1B03 as of Nov 2 2007 ------------------------ + -scan [chanalys] Instructs chanalys to use minimal locking. This may cause the chains report to be incomplete , but it will avoid turning on table locks (which then avoids lkTableLockUpdate and associated errors when run online). [Warning] Unable to acquire table lock on object 2. Chain analysis continuing with -scan option. (14167) 10.1C as of Feb 9 2008 ---------------------- + -agenthost Forces a specific Application Server and all of its agents to communicate only with IPV6 (on a Red Hat Enterprise Linux 6.x). + -cwl Compile Warning List [ABL Session Startup Parameter] Flags instances of statements listed in filename during compilation + -dbgmsg + -errorstack SESSION:ERROR-STACK-TRACE Using -errorstack to start a session, or setting SESSION:ERROR-STACK-TRACE = TRUE within a session results in more accuracy in error reporting, in that when an error is shown, the stack dialog produced by -debugalert as well as LOG-MANAGER output, depicts the accurate stack information from where the error object was originally thrown. + -ipver IPv6 must be explicitly requested at startup in the related server properties file or in the process startup parameters: "-ipver=IPv6". + -pfactor Packing factor. proutil -C idxbuild on databases with 8K blocksizes. + -zdelay + -znolru 10.2B as of Dec 14 2009 ----------------------- + -actionalEnabled + -actionalGroup + -aiencryption [proutil db -C enableencryption] Specifies whether your AI is encrypted or not. If not specified, AI encryption is enabled. + -AppServerKeepalive Session model: Managed or Free Indicates that the client would like to employ the AppServer keepalive protocol on a connection, if supported and enabled by the AppServer or the client. To enable the protocol, specify the allowServerASK or allowClientASK value. To disable the protocol, specify denyServerASK or denyClientASK value. The absence of this property indicates that the default value will be used on the connection. You must set this property only if your AppServer is operating in Stateless or State-free operating mode. Include the -AppServerKeepalive allowServerASK parameter to enable the ASK protocol on ABL/4GL client side: hAppSrv:CONNECT ("-AppService -H -S -AppServerKeepalive allowServerASK"). Or do not include -AppServerKeepalive parameter because the default value is allowServerASK. hAppSrv:CONNECT ("-AppService -H -S ). The ASK protocol on the client is disabled by adding -AppServerKeepalive denyServerASK in the CONNECT method. hAppSrv:CONNECT ("-AppService -H -S -AppServerKeepalive denyServerASK"). + -assemblies Issue PSC00333342 (11.7.0) When working with .NET assemblies in a CHUI project in PDS, if the assemblies directory is not the project directory, the -assemblies parameter is not included in the resultant call to _progres.exe. This is likely leftover from the fact that using assemblies with TTY was not supported in the initial versions of the tool after adopting support for using assemblies in GUI. + -Autostart [proutil db -C enableencryption] Specifies that you will allow your database to autostart authentication to the key store by the specified key store account. If not specified, the database is set to manual startup. Manual startup requires that the user enter the passphrase to authenticate the key store every time the database is opened (by servers, clients, and utilities). + -B2 The number of blocks in the Alternate Buffer Pool + -biencryption Specifies whether your BI is encrypted or not. If not specified, BI encryption is enabled. + -Cipher 6 [proutil db -C load] For an Enterprise database enabled for Transparent Data Encryption, specify -Cipher 6 to indicate that the contents of the dump file being loaded is encrypted. You are prompted to enter the passphrase that was specified when the dump file was created. + -clientASKActivityTimeout [SOAP Web Service] + -clientASKResponseTimeout [SOAP Web Service] + -dslog specifies the DataServer log file name [DataServer for Microsoft SQL Server, DataServer for Oracle] If you do not specify a log file name at startup, then the default dataserv.lg file will be used for logging server information. srvrDSLogFile - corresponds to the -dslog param + -dsmaxport Maximum port range for the DataServer Broker server processes / srvrMaxPort [_probrkr, for MSSQL DataServer or Oracle DataServer] + -dsminport Minimum port range for the DataServer Broker server processes / srvrMinPort [_probrkr, for MSSQL DataServer or Oracle DataServer] + -ecsize Encryption cache size [Database Startup Parameter, Client Connection, For Enterprise licenses only] Specifies the size (in number of encryption policies) of the caches for encryption policies. The encryption cache holds your encryption policies in memory, eliminating the need to read policy records from the database during the encryption and decryption processing. + -edasgnfix + -fmtfix + -imgmem [Client Startup Parameter] Issue: OpenEdge GUI client crashes when rendering images. Program crashes randomly at runtime. the -imgmem startup parameter enables the fix for this issue. From OpenEdge 10.2B onwards, the -imgmem is enabled by default. + -KeyStorePassPhrase ABL clients specify a passphrase for key store authentication by adding the -KeyStorePassPhrase argument, followed by the passphrase to the CONNECT statement to TDE enabled database. + -noevalprops [Client Startup Parameter] + -nogc Disable garbage collection [Client Startup Parameter] + -noimgmem + -oldrccds + -Passphrase Prompt for Passphrase [Database Startup Parameter, Client Connection] + -preloadCLR Preload Common Language Runtime If you do not specify -preloadCLR, the AVM loads the CLR the first time ABL refers to, or uses, a .NET type or object either at compile time or runtime. All of the assemblies listed in the assemblies.xml file are loaded at once. + -reusableObjects Reusable Objects Cache Reusable Objects Cache mechanism was introduced in OpenEdge 10.2B. The Reusable Objects Cache is a feature which improves performance for programs that make use of OOABL classes. The -reusableObjects 0 can be used to disable the Reusable Objects Cache in order to work around issues with this feature. + -shutdownTimeout [immed | maximum |n[ h | m | s]] [proshut db] Specifies the amount of time for normal database activity to stop and users be disconnected before immediately shutting down (killing users still connected). If all normal activity ceases before the time out value is reached, normal shutdown proceeds. Table 62 describes the shutdown time out parameter. If not specified, the default is 10 minutes. The minimum shutdown time out value is 60 seconds (immed) and the maximum time out value is 24 hours (maximum). The -shutdownTimeout parameter is ignored when forced shutdown (-F) is specified. + -utf8fillinjump Issue: When inputting a character, either number, English or Chinese between a string of Chinese characters, the cursor will move to the right by 1 or more chars. The -utf8fillinjump parameter enables the fix. + -utf8intatchar Issue: DISPLAY integer @ variable displays a blank value with the UTF-8 client. The -utf8intatchar parameter enables the fix. It is not necessary to use -utf8intatchar in OpenEdge 11, since this fix is the default behaviour. + -zlrl + -zmicroETIME + -zubvermin + -zwcadminapp [WebClient] 10.2B01 as of Apr 27 2010 ------------------------- No changes 10.2B02 as of Sep 1 2010 ------------------------ + -dbblockhook + -IOEverywhere <0|1> [Client Startup Parameter] If the -IOEverywhere parameter is set to 1 in the .pf file, then it can be overridden on the command line with -IOEverywhere 0. This is only true when the parameter is set to 0 in the .pf file. Until OpenEdge 10.2B02, ABL had restrictions on where an input-blocking statement ( UPDATE, SET, PROMPT-FOR, CHOOSE, INSERT, WAIT-FOR, READKEY, or PROCESS EVENTS) could be used. Input-blocking statements could not be used in a user-defined function, a non-void method, class destructors and some database trigger blocks. For service packs of Release 10.2B, the default is 0, which means the new feature is off and everything works as before. However, when "-IOEverywhere 1" is specified, input-blocking statements may be used in almost every context. There is only one remaining restriction. This occurs if the application: 1. Uses .NET and is in a WAIT-FOR Application:Run() statement. 2. Does a stacked input blocking statement for an ABL non-modal window in one of the places that has always been restricted from doing input-blocking. In these cases, the restriction remains in place. In OpenEdge 11, the default became "-IOEverywhere 1", thus removing the restriction (except for the special cases above) without the need to use the startup parameter. + -togboxfix <0|1|2> Fix the toggle-box behavior between GUI and TTY client Allows selecting the behavior to apply for both GUI and TTY clients: -togboxfix 1 : Do not change the toggle box's value on APPLY VALUE-CHANGED (the GUI behavior). -togboxfix 2 : Change the toggle box's value on APPLY VALUE-CHANGED (the character behavior). -togboxfix 0 (or any value other than 1 and 2) : Use the old inconsistent behavior. 10.2B03 as of Dec 9 2010 ------------------------ + -icubegins <0|1> [Client Startup Parameter] Issue: Executing a FIND-UNIQUE method, a CAN-FIND function or a unique FIND statement against a UTF-8 database using non-default ICU collation fails with error (138) if the WHERE option uses BEGINS operator. Issue is not seen with codepages other than UTF-8, or when using UTF-8 with default Basic collation. For OpenEdge 11.0, the fix is enabled by default. It can be disabled by adding "-icubegins 0". + -nodialogdispose Starting with the OpenEdge 10.2B0206 hotfix we now automatically call Dispose() for .NET dialog boxes once the ShowDialog() method returns. This behavior change was made because the default behavior in .NET is to hide dialogs under the assumption that they will be reused and this was causing memory leak issues. If you do not want the automatic Dispose behavior use the -nodialogdispose startup parameter but be aware that this means you will have to manually call Dispose() against .NET dialogs in order to ensure that they are deleted and the memory is recaptured. + -sw Suppress Warnings. Equivalent to SESSION:SUPPRESS-WARNINGS. [Client Startup Parameter] + -swl Suppress Warnings List: a comma separated list of warning message numbers to suppress. Equivalent to SESSION:SUPPRESS-WARNINGS-LIST. [Client Startup Parameter] + -ununcp 10.2B04 as of Mar 8 2011 ------------------------ + -keeptargetlfe Restores a backup without enabling large files. [prorest] By default, restoring a database backup that has large files enabled, enables large files on the target database, even if the target is an existing database without large files enabled. Use this parameter to restore a backup without enabling large files on the target database. -z Information about sort files and sort merge pool created/used by idxbuild. Also in 11.1.*. Reports the messages: %BThread memory usage #threads: %d Required: %J Limit: %J In use: %J %B %s: numEntries: %i %B Threads requested: Data scan: %d, sort: %d, merge: %d, sort groups %d %B*** Used %l in-memory sort buffers out of %l (%j MB out of %j MB) + -rusage Reports resource statistics [proutil db-name -C idxbuild] When specified, index rebuild reports resource statistics including user and system CPU usage and approximate disk reads and write I/O statistics. + -TF Memory usage factor [idxbuild] Introduced in OpenEdge 10.2B04, but 10.2B06, 11.1.1 or later are advised where several issues related to the -TF parameter were addressed. This is the percentage of system memory that can be allocated for merging sort buffers when sorting index keys during the index rebuild process. In the past, there was only one sort merge buffer, and when the sort merge buffer became full, the contents were written to the file system. The default value of -TF is 50 (for 50%). Setting -TF 0 results in the pre-10.2B04 behavior. + -TMB : Merge block size [idxbuild] This is the size of the blocks used to merge sorted blocks together. This value can now be specified separately from the sort block size (-TB). The default value for -TMB is the -TB value. The minimum value is the -TB value. If -TMB is set to a value less than -TB, index rebuild will exit. + -schlockwq Alters the schema locking algorithm [Database Startup Parameter] When the database broker is started with the -schlockwq switch, the schema lock scheduler forces a shared schema lock request to wait when an exclusive schema lock request is queued. Once an exclusive schema lock request is queued, it appears to all subsequent schema lock requests that an exclusive schema lock has been granted (meaning all subsequent schema lock requests will queue). Without the -schlockwq switch, shared locks continue to be granted, even though an exclusive lock is queued. With the -schlockwq switch, wake up of users waiting for a schema lock is performed in the order they were received. Without the -schlockwq switch, all users are awoken whenever any schema lock conflict is resolved, causing a race to see which user gets the available lock. When running with the -schlockwq switch enabled at broker startup, only those users allowed to get the schema lock will be awoken. 10.2B05 as of Sep 6 2011 ------------------------ No changes 10.2B06 as of Mar 19 2012 ------------------------- + -actionalConsumer + -datascanthreads [idxbuild] When -datascanthreads is specified, it invokes a multi-threaded data scan that spawns n threads for the data scan phase. The data being scanned, must meet all of the following criteria for a multi-threaded data scan to occur: * The data area being scanned must be a Type II area * No index within the data area being scanned is also being rebuilt * No index associated with the data area being scanned is a word index * Index rebuild must be run with the "sort" option, that is answering "y" when asked if you have enough room for sorting. If any requirement is not met, the data scan is performed using the original single threaded mechanism. If not specified, the -datascanthreads value defaults to 0, also indicating the original single threaded mechanism. + -lru2skips LRU alternate buffer pool force skips [Database Startup Parameter] + -lruskips LRU force skips [Database Startup Parameter] + -mergethreads [idxbuild] Specifies the number of concurrent threads to spawn during the sort/merge phase of index rebuild that merges the key entries in the sort blocks produced by the data scan phase for an individual index sort group. A value of 0 (the default) results in the original, pre-Release 11.1 behavior of one thread per index sort group. A value of 1 also results in the original behavior of one thread per index sort group but the sort/merge is performed by a newly spawned thread rather than by the thread assigned to the individual index sort group. + -Nmsgwait Message Wait [Database Startup Parameter] Use Message Wait (-Nmsgwait) to indicate the number of seconds a server waits for a remote network message before checking for other events such as a database shutdown or forced disconnect of a remote client. + -noUnicodePrinters + -prefetchDelay <> Prefetch delay / Server network message wait time [Database Startup Parameter] Use Prefetch delay (-prefetchDelay) to enable a delay when sending the first network message for queries with prefetch capabilities. Prefetch delay is off by default, indicating the that first network message is sent as soon as it contains the first record of the query. + -prefetchFactor Prefetch factor / Prefetch message fill percentage [Database Startup Parameter] Establishes a percentage of a network message required to contain prefetched data before sending the message to a waiting remote client. + -prefetchNumRecs Prefetch Num Recs / Minimum records in prefetch message [Database Startup Parameter] The number of prefetch records to put in a network message before sending the message to a waiting remote client. Default: 16, min: 1, max: 32766 + -prefetchPriority Prefetch Priority / Suspension queue poll priority [Database Startup Parameter] The number of prefetch records to add to a network message. Default: 0, min: 0, max: 32766 Use Prefetch Priority (-preFetchPriority) to utilize a "pollskip" that adds n records to the network message of an in-process prefetch query without additional polling. Adding more than one record to the message at a time can greatly reduce the number of poll() calls being made on a large database configuration. The expected result is that reducing poll() calls improves overall system performance by decreasing the "System CPU" cycles allow for increased "User CPU" cycles. The pollskip only occurs if the previous poll() call returned nothing waiting. Promon > R&D > 4. Administrative Functions > 7. Server Options 1. Server network message wait time: 2 seconds 2. Delay first prefetch message: Disabled 3. Prefetch message fill percentage: 0 % 4. Minimum records in prefetch message: 16 5. Suspension queue poll priority: 0 + -rereadfields Force the AVM to always re-read the full record if an error 8826 would be raised: Field from record (recid ) was missing from FIELDS phrase. (8826) + -utf8keylabel <0|1> [Client Startup Parameter] Issue: triggers with extended characters do not work with a UTF-8 client. 10.2B07 as of Sep 7 2012 ------------------------ + -clientConnectTimeout [Web Services connections] + -SQLQuotedRowid [ std | value] SQL rowid identifier [Database Startup Parameter] Specify behavior of the string "rowid": std — specify std to indicate that all instances of the quoted string "rowid" are interpreted as an SQL identifier (such as a column name). value — specify any string other than std to indicate that all instances of rowid, quoted or not, are interpreted as the SQL rowid function. 10.2B08 as of Nov 12 2013 ------------------------- + -freeTF <0|1> [idxbuild] Specifies whether to free the merge buffer memory explicitly or leave the free to the operating system at the completion of IDXBUILD. Value of n Action 0 - Do not explicitly free merge buffer memory. The default for Windows 64-bit. 1 - Explicitly free merge buffer memory. The default for all Unix platforms and Windows 32-bit. To improve performance, the merge buffers in the -TF pool are pointer swapped rather than using strcpy(), which results in the list of allocated memory chunks being in sort order rather than allocated order. When the buffers in the -TF pool are freed in an order other than they are allocated, there can be severe performance problems on Windows 64-bit. By setting -freeTF 0 on Windows 64-bit, the allocated memory is freed by the operating system when IDXBUILD completes. + -pollset Use pollset mechanism for client/server [Database Startup Parameter] Also in '11.2 as of Feb 13 2013' + -utf8chardisp See '11.2.1 as of Apr 29 2013' 11.0 as of Dec 2 2011 --------------------- Does not include - -actionalConsumer introduced in 10.2B06 as of Mar 19 2012 - -clientConnectTimeout introduced in 10.2B07 as of Sep 7 2012 - -datascanthreads introduced in 10.2B06 as of Mar 19 2012 - -freeTF introduced in 10.2B08 as of Nov 12 2013 - -lru2skips introduced in 10.2B06 as of Mar 19 2012 - -lruskips introduced in 10.2B06 as of Mar 19 2012 - -mergethreads introduced in 10.2B06 as of Mar 19 2012 - -Nmsgwait introduced in 10.2B06 as of Mar 19 2012 - -noUnicodePrinters introduced in 10.2B06 as of Mar 19 2012 - -pollset introduced in 10.2B07 as of Sep 7 2012 - -prefetchDelay introduced in 10.2B06 as of Mar 19 2012 - -prefetchFactor introduced in 10.2B06 as of Mar 19 2012 - -prefetchNumRecs introduced in 10.2B06 as of Mar 19 2012 - -prefetchPriority introduced in 10.2B06 as of Mar 19 2012 - -rereadfields introduced in 10.2B06 as of Mar 19 2012 - -SQLQuotedRowid introduced in 10.2B07 as of Sep 7 2012 - -utf8chardisp introduced in 10.2B08 as of Nov 12 2013 - -utf8keylabel introduced in 10.2B06 as of Mar 19 2012 - -zdbo 9.1D - -zubvermin 10.2B as of Dec 14 2009 + -actionalDBEnabled + -ai + -checkneedsattention + -collop <0|1|2|3> [ABL Client Startup Parameter, Database Startup Parameter] Note: database startup parameters -cpcoll -icucistr and -collop are not listed in the VST table _DbParams Issue: Query using BEGINS operator fails to find accented characters. BEGINS and MATCHES operators do not always use collation tables. COMPARE with MATCHES operator also ignores collation. As a result, a query may not always return the expected result set. BEGINS has two behaviors, one for indexes (which does use the collation) and one for non-index comparisons (which does not use the collation). This causes issues in applications that process character data that contains special characters such as diacritical marks, as the result set of a query with a BEGINS operator on a field will depend on whether or not an index which includes that field is used. OpenEdge 11.0 introduces a partial fix and supports collations for the BEGINS operator only. 0 - Old behaviour 1 - The fix must be explicitly enabled by including the -collop 1 startup parameter for both the client and database. Issue: The ABL MATCHES operator does not support collations. MATCHES can fail to return expected matches when using UTF-8 collations. MATCHES ignores collation when character data contains special characters. 11.7.0, 11.6.1 or 11.5.1.013 2 - Use -cpinternal UTF-8 -collop 2. Please be aware that enabling -collop 2 will considerably impact the performance of the MATCHES operator due to the nature of the underlying algorithm. Using ICU-* collations will further compound the performance impact due to their increased complexity. Customers making extensive use of the MATCHES operator are advised to test and benchmark their applications with -collop 2 in place before deciding whether to implement it in production. 3- Use -cpinternal UTF-8 -collop 3 if collation support in a UTF-8 session is required for both BEGINS and MATCHES then use the following startup parameters: + -mtpmsize MT cache Size Use -mtpmsize to specify the number of entries in the multi-tenancy partition cache. At startup, a primary and secondary multi-tenancy partition cache are allocated, each with the number of entries specified by the -mtpmsize startup parameter; INCREASETO only modifies the size of the secondary cache. + -noneedsattnthread + -noroutineinwhere No Routine In Where [Client startup parameter] Superceeds the -noudfinwhere startup parameter to restrict the WHERE clause from containing a class method, user-defined function, or a class property. It adds in the ability to detect and block the same in OO property references and OO method calls. The error message raised if this parameter is used is: "Found routine in WHERE when startup -noroutineinwhere given. (16015)" PSC00352161 (11.7.0) The -noroutineinwhere parameter does not catch some cases such as properties with implementation or x:y types of expressions. + -nottdelay No Delay for Static Temp-table Initialization Prior to OpenEdge 11.0, a static temp-table is instantiated the moment the procedure or class that defines it is instantiated. For code that defines larger numbers of temp-tables this can cause a significant delay while instantiating the procedure/class. Starting with OpenEdge 11.0, by default the instantiation of those temp-tables is delayed to the point in the code where records in the temp-table would be queried or created. The main goal of this feature is to spread the performance impact, which removes the bottleneck during procedure instantiation and improving overall response times. A secondary goal is to avoid spending resources if the procedure defines a temp-table that it doesn't actually use. (A common example is that a set of temp-tables is defined in an include file - where procedures do not always use all of those temp-tables.) The -nottdelay startup parameter is used to revert back to the pre-OpenEdge 11 behavior. It should only be used as a workaround if there is an issue with the new way the temp-tables are managed. Note that such issues should be considered defects, and should be reported to Progress Software for further investigation. + -noutf8intatchar + -SQLAutoStats SQL Autonomous Update Statistics [Database Startup Parameter] Set the value of this parameter as ON, during startup, to start the Autonomous Update Statistics (AUS) service. Once the value of the parameter is set, it is remembered for the lifetime of the server and for all connections. Promon > R&D > 4. Administrative Functions > 7. Server Options > 10. SQL Autonomous Statistics + -SQLAutoStatsThreshold + -srcdbg + -ttbaseindex Base index of the temp-table [ABL Session Startup Parameter] Specifies a range of temp-table indexes for which you want to collect index statistics. + -ttbasetable Base table of the temp-table [ABL Session Startup Parameter] Specifies a starting temp-table number in a range of temp-tables for which you want to track access statistics. + -ttindexrangesize Index range size of temp-table [ABL Session Startup Parameter] Specifies the number of indexes of temp-tables for which you want to collect statistics. + -tttablerangesize Table range size of temp-table [ABL Session Startup Parameter] Specifies the number of temp-tables for which you want to collect statistics. + -zbrokerDebug + -znoposirc Related to the field position-independent r-code feature introduced in OpenEdge 11.0 (Oracle DataServer)? PSC00352474 (11.7.0) When running r-code while using the -znoposirc parameter the session crashes. The following stack trace may be seen in protrace or DMP file analysis: scBuildSignature scrcode_to_flds rnreloc rnproc_entry + -zqtp 11.1 as of Jun 15 2012 ---------------------- - -actionalEnabled Introduced in 10.2B as of Dec 14 2009 - -actionalGroup Introduced in 10.2B as of Dec 14 2009 + -lru2skips See '10.2B06 as of Mar 19 2012' + -lruskips See '10.2B06 as of Mar 19 2012' + -mergethreads See '10.2B06 as of Mar 19 2012' + -Nmsgwait See '10.2B06 as of Mar 19 2012' + -noUnicodePrinters See '10.2B06 as of Mar 19 2012' + -prefetchDelay See '10.2B06 as of Mar 19 2012' + -prefetchFactor See '10.2B06 as of Mar 19 2012' + -prefetchNumRecs See '10.2B06 as of Mar 19 2012' + -prefetchPriority See '10.2B06 as of Mar 19 2012' + -rereadfields See '10.2B06 as of Mar 19 2012' + -utf8keylabel See '10.2B06 as of Mar 19 2012' + -deprecated1 + -deprecated2 + -deprecated3 + -deprecated4 + -LGovernor Lock Governor Specifies the percentage of the lock table that a tenant can occupy. Lock governor prevents a tenant from acquiring all the locks in a table. Lock governor applies to the default tenant and regular tenant. This governor does not apply to super-tenants and non multi-tenant databases. + -nGovernor Login Governor Specifies the maximum number of users that may login for each tenant in a multi-tenant database. Login governor prevents a tenant from using all the database connections, and prevents other tenants from logging in. Login governor applies to the default tenant and regular tenant. This governor does not apply to super-tenants and non multi-tenant databases. Promon > R&D > 4. Administrative Functions > 11. Adjust Governor options + -noutf8fillinjump 11.2 as of Feb 13 2013 (compared to as of Sep 7 2012) ---------------------- + -clientConnectTimeout See '10.2B07 as of Sep 7 2012' + -SQLQuotedRowid See '10.2B07 as of Sep 7 2012' + -defaultscrolling Default Scrolling [ABL Session Startup Parameter] Makes scrolling the default behavior for all statically defined queries + -ideembedwarn + -nethash [ABL client connection parameter for .NET controls] + -pollset Use pollset mechanism for client/server [Database Startup Parameter] + -undothrow Issue: If a method THROWs an AppError, the CATCH block in the calling method does not catch it. Thus error conditions can go unhandled and result in unexpected behaviors. Multiple ways to solve this: * Use a RETURN ERROR statement instead of the UNDO, THROW in the called method. As per traditional error handling, this returns from the called routine first and raises the error condition in the calling routine. By passing an AppError object, the error will be thrown, so it can be caught. * Make sure the calling class uses the ROUTINE-LEVEL ON ERROR UNDO, THROW or BLOCK-LEVEL ON ERROR UNDO, THROW directives. As per documentation, these options explicitly change the default behavior to ensure all errors get thrown as AppErrors. * Starting with OpenEdge 11.2 this can be enforced without code changes, by specifying the -undothrow startup parameter on the compiling session. Issue PSC00328731 fixed in 11.5.1.0: -undothrow 2 does not throw errors from blocks with no explicit error directive that are inside a user interface trigger. 11.2.1 as of Apr 29 2013 ------------------------ + -utf8chardisp 3 Addresses an issue with DISPLAY of a multi-byte CHAR value @ an INT or DEC field in a frame, when using -cpinternal UTF-8. This introduced a regression for subsequent DISPLAYs of the frame when displaying the original INT or DEC field in the frame. The values would be pushed to the right, and any other fields on the frame to the right of the field would not appear. 11.3 as of Jul 17 2013 ---------------------- + -ailist [rfutil] Identifies a file containing a list of AI area files. + -dbrestrict [prorest] Protects the restored database from updates by other users by putting the database in a restricted access mode where restrict-type is one of the following values: * rollforward — Indicating that the next allowable activity on this database is rolling forward after-image files; * datamove — Indicating that the next allowable activity on this database is moving data with the datamove utility; * partitioncopy — Indicating that the next allowable activity on this database is copying data with the partitionmanage copy utility. Adding -dbrestrict enables the same restrictions as PROUTIL DBRESTRICT. + -freeTF See '10.2B08 as of Nov 12 2013' + -pausefix Issue: Default window displays when PAUSE NO-MESSAGE is used in GUI for .NET The -pausefix enables the following behavior: When executing 'PAUSE n', with or without the NO-MESSAGE option, the AVM should pause for n seconds even if the window governing the pause is not visible or does not have a status area. If the governing window isn't visible it should not be made visible to execute the pause. + -zextendSyncIO [proutil -C bigrow, Unix only] Since 11.3.0 proutil -C bigrow: * BI extents written are flushed from the file system cache with an fdatasync() call and buffered I/O is only used again once finished grow/formatting the clusters. * This rework also extends to the runtime database when for example a long running transaction necessitates the format of new biclusters added to the bi chain. The -zextendSyncIO parameter restores the old behaviour: BIGROW uses a buffered file handle to grow the bi file and the buffered file handle does unbuffered I/O 11.3.1 as of Sep 19 2013 ------------------------ + -SQLLockWaitTimeout Lock Wait Timeout [Client Connection, Database Startup Parameter] Use this parameter to specify the number of seconds to wait when a lock conflict occurs. This value applies to all conflicts that occur while using SQL applications. The default value is 5 seconds. 11.3.2 as of Jan 27 2014 ------------------------ No changes 11.3.3 as of Sep 25 2014 ------------------------ + -TXERetryLimit Transaction End (TXE) Lock Retry Limit Default: 0, min: 0, max: 100,000 where n - The number of tables for which you want to track access statistics. Use Transaction End (TXE) Lock Retry Limit (-TXERetryLimit) to specify the number of number of times a connection will re-try to obtain TXE lock after a 1ms nap before getting queued. The default value is 0 (no behavior change). The Transaction End (TXE) Lock is required for crash recovery to work properly. The lock single threads "micro-transaction" type updates within the storage engine, as well as assures that database changes are properly ordered when a transaction ends. A high degree of conflict queuing this lock can severely impact performance. The cost of managing the queue and waiting on a semaphore, as well as awakening waiting requests, while keeping things "fair" carries a high performance penalty. When the connection spins on the TXERetryLimit, rather than waiting on a semaphore, contention shifts from the TXE Lock to the TXQ latch, but the lower level TXQ latch is a much lighter-weight mechanism, and because of that, improves the overall performance of the system. + -zet 11.4 as of Jul 25 2014 (compared to 11.3.2 as of Jan 27 2014) ---------------------- -z Information about sort files and sort merge pool created/used by idxbuild. As addition to the messages introduces in 10.2B04 and 11.1 reports: %BThread %i created file %s%s, dirIndex: %d, fd: %i (17592) %BGroup %d, Thread %i created file %s%s, dirIndex: %d, fd: %i (17593) ***Useage of merge pool for local and/or shared indexes: %BSort pool exhausted memory at %i entries, expected %i. (17594) %LProcess memory %j of %j in use (17596) %LMax merge pool entries estimated at: %i w/memory usage: %j (17597) + -clrins + -csoutput [proutil -C dbanalys] Specifies that DBANALYS output the analysis data to text files in addition to the screen + -csfilePrefix [proutil -C dbanalys] When -csoutput is specified, pref-name indicates a file name prefix. The database name is used by default. All remaining elements of the file name are not customizable. + -fieldsep [proutil -C dbanalys] + -verbose [proutil -C dbanalys] When -csoutput is specified, the first row of the output files contains header names for each column of output. + -nosplash Turns off display of the splash screen. By default, the OpenEdge GUI client and the WebClient display a splash screen during startup. The screen, which is a blue rectangle with the words “Powered by Progress Software” disappears when the OpenEdge application starts. Old way: in the [startup] section of the Progress initialization file (progress.ini by default) add: nosplash=yes Client authentication has been implemented in the OpenEdge 11.4 ABL client for consuming SOAP Web Services. This also includes the WSDL Analyzer (bprowsdldoc) command-line utility: + -sslAuth Specifies if access to a SOAP service requires SSL client authentication. Set this to ssl to enable client authentication for SOAP access. If you set this to basic, the connect method ignores client authentication for SOAP access. + -sslKeyFile The location of the client certificate. If you do not specify an absolute path of the client certificate file, the connection operation searches the $DLC/keys folder for the client-certificate-file-name.pem file. This option must be set only if -sslAuth parameter is set to ssl. + -sslKeyPwd The SSL client certificate password in clear text or encoded format. + -WSDLAuth Authentication-type Specifies if the access to a WSDL file requires SSL client authentication. Set this to ssl to enable SSL client authentication for WSDL access. If you set this to Basic, the connect method ignores client authentication for WSDL access. + -WSDLKeyFile Specifies the location of the client certificate. If you do not specify an absolute path of the client certificate file, the connection operation searches the $DLC/keys folder for the client-certificate-file-name.pem file. This option must be updated only if -WSDLAuth parameter is set to ssl. + -WSDLKeyPwd Specifies, in clear text or encoded format, the password of the client certificate. This option must be updated only if -WSDLAuth parameter is set to ssl. + -zLPPartitionLocks + -zLPRecordLocks + -zLPTableLocks + -znoencrypt + -znoolfarc 11.5 as of Dec 5 2014 (compared to 11.4 as of Jul 25 2014) --------------------- + -ccvalidate + -cstack + -fixcursorjump + -MaxWorkerThreads [ASP.NET?] + -minhybridprops + -nocandodomain Issue: The CAN-DO function returns different results if @ signs are used in string patterns before and after 11.0. The -nocandodomain reverts the behavior implemented in 11.0. + -nocolon No Colons for Side Labels [ABL Session Startup Parameter] At compile time, colons are automatically appended to side labels for static widgets. To create side labels without colons, compile the r-code with -nocolon in effect. Running OpenEdge with -nocolon does not affect precompiled procedures. Side labels created by code that was not compiled with -nocolon in effect will include colons even if the current session is running with -nocolon active. See RCODE-INFO:LABELS-HAVE-COLONS attribute. + -sectok [PASOE (_mproapsv)] + -uburl AppServerDC://0.0.0.0:43420/ [PASOE (_mproapsv)] + -znoguardpage 11.5.1 as of May, 2015 ---------------------- + -silent no longer reports block status [IDXFIX] + -rusage is added to report runtime statistics [IDXFIX] When specified, idxfix reports resource statistics including user and system CPU usage and approximate disk reads and write I/O statistics, and elapsed time (PSC00325788). 11.6 as of Oct 16 2015 (compared to 11.5 as of Dec 5 2014) ---------------------- - -checkneedsattention Introduced in '11.0 as of Dec 2 2011' + -batchwidth Batch client character width The value for is a number between 1 and 320. Values less than 0 cause an error at startup. Values greater than 320 are silently changed to 320. + -cdcsize CDC cache size of both the primary and secondary CDC caches combined. Default: 2000 if CDC is enabled and 200 if CDC is not enabled, min: 20, max: 1400320 In single-user mode, the primary cache is not used, and the entire size is allocated to the secondary cache. In multi-user mode, 75 percent of the cache size is allocated to the primary cache, and the remainder to the secondary. However for values smaller than 400, the size is split evenly between the two caches. You can increase the size of the secondary cache at runtime with PROUTIL INCREASETO. + -crStatus Crash Recovery Status Interval (between progress approximation messages for the redo and undo phases of crash recovery). + -crTXDisplay Crash Recovery Transaction Display + -enforceMm Enforce Mm [Client Connection, Database Startup Parameter] Specifies that the behavior of the Message Buffer Size (-Mm) startup parameter follow prior releases. OpenEdge uses message buffers to move records (messages) between servers and remote clients. The size of the message buffer is specified with -Mm. Starting in OpenEdge Release 11.6, the value of -Mm is not required to agree between the server and the client, however in releases prior to OpenEdge 11.6, the value of -Mm had to be specified the same for both the client and the server or the connection is refused. Use Enforce Mm (-enforceMm) to require agreement between the client and server values of -Mm as in earlier releases. + -entityExpansionLimit Protects against XML entity expansion attacks. + -refreshfix + -retainfocus + -SQLTruncateTooLarge {ON|ALL|OFF|OUTPUT} Authorized Data Truncation [Client Connection, Database Startup Parameter] OUTPUT - Set this parameter to OUTPUT to truncate the data returned to the user when its size exceeds the column size. All SQL operations such as comparison, sorting use actual data and only the output is truncated. ON/ALL - Set this parameter to ON or ALL to perform SQL operations on truncated data. Also the data returned to the user is also truncated when its size exceeds the column size. OFF - When the parameter value is set to OFF, data will not be truncated and an error is returned. + -SQLWidthUpdate ON Autonomous Schema Update [Database Startup Parameter] Set the value of this parameter as ON, during startup, to resolve the SQL width problem by updating the SQL column width in schema automatically when Authorized Data Truncation(ADT) occurs for data in a column. Once the value of the parameter is set, it is remembered for the lifetime of the server and for all connections. If this parameter is set to ON during startup, the Authorized Data Truncation(_SQLTruncateTooLarge) parameter is also enabled irrespective of whether ADT was enabled during startup unless specified otherwise using connection URL. + -sslciphers SSL Server ciphers / PSC_SSLCLIENT_CIPHERS. Default: AES128-SHA256 [Database Startup Parameter] + -sslprotocols SSL protocol / PSC_SSLCLIENT_PROTOCOLS. Default: TLSv1.2 + -sslSOAPCiphers SSL Server ciphers + -sslSOAPProtocols SSL protocol + -sslWSDLCiphers SSL Server ciphers + -sslWSDLProtocols SSL protocol Supported protocols, ciphers, and certificates for Progress OpenEdge clients and servers https://documentation.progress.com/output/ua/OpenEdge_latest/gscsv/supported-protocols,-ciphers,-and-certificates-f.html + -strictEntityResolution <0|1> Issue: In OpenEdge 11.6 the default behavior is to use strict entity resolution when trying to validate an XML document against a DTD file. 0 returns to the old (less secure) behavior. + -suppressChunkedRqs + -utf8chkfmt -crStatus and -crTXDisplay were deactivated in 11.6.0 (there are active again in 11.6.1). 11.6.1 as of Feb 16 2016 ------------------------ + -norunextchars + -useSessionTZ <0|1> 0 - System's time zone is used for assignments between DATE/DATETIME/DATETIME-TZ values (default in version 11.6.1). 1 - SESSION:TIMEZONE is used (default in version 11.7.x and later). -collop Issue PSC00343788: The collation-sensitive MATCHES operator enabled by -collop 2 incorrectly matched substrings with different numbers of trailing spaces. For example, "a a" (with one space) MATCHES "* *" (with two spaces) returned TRUE. -sslSOAPProtocols and -sslSOAPCiphers Issue PSC00344081: When encountering a SOAP service providers configured with protocol TLSv1 & cipher AES128-SHA, the default connection is failing (as OE 11.6 uses default SSL protocol as TLSv1.2 & cipher AES128-SHA256). This causes the need to include the -sslSOAPProtocols and -sslSOAPCiphers parameters in the connection, or to set the corresponding environment variables (below). It is also important that the protocols and ciphers to be specified in a specific order (demonstrated in the workaround). Environment variables: PSC_SSLCLIENT_CIPHERS, PSC_SSLCLIENT_PROTOCOLS The problem with having to do this is that it is anything but apparent that this is the problem from the error messages that are returned. 11.6.2 as of May 20 2016 ------------------------ + -eventfix <0|1> [Client Starup Parameter] Issue: All fields in a frame will fire leave trigger except for the last one. This behavior has been present since at least 9.1E04. Use -eventfix 1 to enable the fix. + -marshalUndo <0|1> Issue: When a dataset which contains a temp-table which is defined without "no-undo" is sent over the appserver, the "undo" attribute of the buffer always shows "no". The UNDO state is set in a flag that is marshaled over but it is never read when re-creating the dynamic information on the other side. The temp-table undo attribute value over Appserver is not respected. 0 - old behaviour (default in 11.6.2) 1 - fix is enabled (default for 11.7+) + -OSUser [Database Connection, For use with the OpenEdge Authentication Gateway only ] + -secsize Security cache size [Database Connection, For use with the OpenEdge Authentication Gateway only] The size, in number of cache entries, of the primary and secondary security caches. Each entry consumes approximately 450 bytes. Default: 512, min: 0, Max: 32768 + -stslogginglevel <0-5> STS logging level [Database Connection, For use with the OpenEdge Authentication Gateway only] The logging level: 0 — none 1 — fatal errors only 2 — all errors 3 — all errors and warnings 4 — all errors, warnings, and informational messages 5 — all errors, warnings, informational, and debug messages Values less than 0 generate an error; values greater than 5 are reset to 5 internally For use with the OpenEdge Authentication Gateway only, use STS logging level (-stslogginglevel) to specify the logging level value for STS client interface logging. This client-side startup parameter can aid you in debugging authentication problems in an OpenEdge Authentication Gateway deployment. 11.6.3 as of Sep 8 2016 ------------------------ + -cstackPrintopt C stack print option Use the C stack print option (-cstackPrintopt) parameter to define the behavior of the C stack trace mechanism for protrace files generated when a SIGUSR1 signal is sent to the process as part of a kill command or proGetStack. Set n as follows to indicate the status of C stack generation: 0 — C stack generation is enabled. This is the default. 1 — For use with GDB installs. A value of 1 will execute the gstack script. This process runs as a separate process that must be spawned by a privileged user in order to generate a trace stack for another process. 2 — C stack generation is disabled. Caution: -cstackPrintopt 1 enables the gstack script to run as root. This poses a security risk. Restricted access to the script is advised. + -httpBasicPwd + -httpBasicUid + -noclr No CLR (PAS for OpenEdge / All Windows clients?) Disable the Common Language Runtime (CLR) component, which manages the execution of .NET programs. + -unknownToNull <0|1> Mapping the Unknown value to null in .NET Issue: PSC00348858 Before 11.7, if you set a .NET property that is defined as a mapped type (a base type) to the Unknown value (?), the property's value would be set to the default value for its data type. Starting in 11.7, the value will be set to null if the property in .NET is defined as a nullable type. For example, the string data type in .NET is always nullable, so you will get null instead of the empty string. Other base types are not nullable by default, but they can be explicitly defined as nullable in .NET with special syntax. If you set a property of some base type other than string to the Unknown value (?), it may be set to null, depending on how the .NET class was written. Most often these types are not nullable and the behavior will be the same as it was before, i.e., you will get the default value for the data type. Note that when you pass the Unknown value (?) as a parameter to a .NET method, the target variable in .NET is already set to null if the type is nullable. This new behavior is only for setting properties. 0 - the old behavior (the default in 11.6.3) 1 (or greater) - the new behavior (the default in 11.7) 11.6.4 as of Oct 3 2017 ----------------------- + -zwiderposrc [DataServer for Oracle] A field referenced in the FIELDS phrase of the query has a FOREIGN-POS of 256 or higher. Due to a limitation in the r-code, the number of addressable fields in the FIELDS phrase for a DataServer query is restricted to 255 columns. This was introduced by the field position-independent r-code feature introduced in OpenEdge 11.0. - Application code must be re-compiled with -zwiderposrc in place. - R-code compiled with this switch is forward compatible only, e.g. r-code built with the -zwiderposrc switch will not be compatible with older versions of OpenEdge 11. - If the code uses dynamic queries then the -zwiderposrc startup parameter must be used at runtime. DataServer applications that are not facing issues with 255 position field position limit can continue without compile time switch. 11.7 as of Mar 27 2017 ---------------------- + -baseuserindex Starting index number per user for statistics range + -baseusertable Starting table number per user for statistics range + -userindexrangesize Number of indexes per user included in statistics collection + -usertablerangesize Number of tables per user included in statistics collection + -catchStop 1 This feature can be used to CATCH a STOP condition. + -compileroptionsfile Specifies a file name (*.cf). An extension to the Compiler which allows the ABL developer to request the compiler perform additional checks. + -debugPASOE + -diagDir Diagnostic directory + -diagEvent Diagnostic events value (LockTable:0,BiThold:0,SysErr:0) + -diagEvtLevel Diagnostic event level + -diagFormat Diagnostic data format + -diagFS Diagnostic field separator + -diagPause Diagnostic pause length + -diagPrefix Diagnostic prefix value + -diagProc Diagnostic procedure Promon > R&D > 4. Administrative Functions > 14. Diagnostic Data Collection Current Diagnostic Data Collection Settings: 1. Diagnostic directory: "" 2. Diagnostic field separator: ' ' 3. Diagnostic pause time: 0 4. Diagnostic prefix value: diagEvent_ 5. Diagnostic report format csv 6. Lock Table Overflow: 0: Data collection disabled 7. BI Threshold: 0: Data collection disabled 8. System Error: 0: Data collection disabled 9. Collect enabled diagnostic data now + -lockstacktrace + -nojoinhint Join Hint [Compile time parameter, DataServer for Oracle only] Disables the USE_MERGE default query-tuning hint for OUTER-JOIN queries. If only a few records are needed out of a large result set, the USE_MERGE default can be inefficient. + -numCheckpointStats Number of checkpoint statistics to record (default: 32, min 8, max 1024) + -redundantlockdiag <0|1> Toggle redundantlockdiag setting (for use when directed by Progress Technical Support only) promon/R&D/4. Administrative Functions/12. Toggle redundantlockdiag setting + -servername A part of the handshake when a Web Service provider enables SNI (Server Name Indication) in their webservice [ABL Client CONNECT() method] + -soapServername A part of the handshake when a Web Service provider enables SNI (Server Name Indication) in their webservice [SOAP connections] + -wsdlServername A part of the handshake when a Web Service provider enables SNI (Server Name Indication) in their webservice [WSDL connections] The -soapServername and -wsdlServername are not available in 12.0 + -usernotifytime Database Client Notification Default: 0, min 0, max 86400 The time, in seconds, of how often a client polls for notification of a schema change. The default is 0, indicating that no polling occurs. The minimum non-zero value is 1; the maximum is 86400 (for 24 hours). Use Database Client Notification (-usernotifytime) to specify how often a client polls the database to see if a schema change is in process. If no updates to schema are anticipated, due to index activation or rebuild, while the database is online, you can disable notification, or set the notification value to a very high number. If a change is required, the time between polls can be modified with PROMON or through the _DbParams VST. However, if the value is changed from 0 to a non-zero value, currently connected clients will not observe the change; only new clients will poll to receive the polltime value. Promon > R&D > 4. Administrative Functions > 7. Server Options > 8. User notify time + -zclrlog -ipv6 ESQLC clients can specify an IP protocol version using a parameter: progress:T:myhost:5000:mydb:[-ipv6] The parameter is also available to use with connection URLs for the SQLDump, SQLoad, and SQLSChema utilities. 11.7.1 as of Jun 14 2017 ------------------------ + -eolescapefix Issue PSC00344711 ? Sealed data error loading audit data .ad files into a new UTF-8 database with the Data Administration tool if the data contains escaped \n characters. -ipver Its value is now displayed correctly when querying the _db_params VST table, when connecting with a shared memory client. 11.7.2 as of Oct 24 2017 ------------------------ + -limitLgPayload Limit log file payload When enabled, it will avoid populating the .lg file messages with the user name, tty, and system name information. (4281) Server started by on . (452) Login by on . (453) Logout by on . (742) Login usernum 24, userid , on . (7129) Usr 24 set name to . (17961) User 24 set tty to . (7129) Usr 24 set name to . Promon > R&D > 4. Administrative Functions > 7. Server Options > 9. Limit .lg message payload. + -omitLgMsgs Omit log messages The comma-separatedl list of database messages (upto 16 messages) to omit reporting to the database log file. Fatal error messages cannot be suppressed with this parameter. The message numbers are not validated at startup, and invalid message numbers are ignored. Embedded spaces are not allowed. Promon > R&D > 4. Administrative Functions > 15. Database log file management 1. Omit .lg file messages (-omitLgMsgs): Not Enabled 2. Limit .lg file payload (-limitLgPayload): Not Enabled 11.7.3 as of Apr 27 2018 ------------------------ + -emptyFields + -hashLatchFactor Buffer pool hash table latch percentage [Database Startup Parameter] + -lgArchiveDir Database log file archive directory [Database Startup Parameter] + -lgArchiveEnable Archive database log file before truncation [Database Startup Parameter] + -lgTruncateFrequency Frequency of database log file truncation [Database Startup Parameter] Valid values are 0 thru 8. -1 means "Not Enabled" 0:daily, 1,2,...,7: indicating weekly, each Monday,Tuesday,..., or Sunday, 8:monthly, on the last day of each month. Use in conjunction with -lgTuncateTime startup parameter to determine the time of the truncation on thespecified days. + -lgTruncateSize The maximum size the database log file can grow before truncation (in megabytes) + -lgTruncateTime Time of day for the database log file truncation (in hours and minatues: HH:MM) Promon > R&D > 4. Administrative Functions > 15. Database log file management 3. Archive directory (-lgArchiveDir): Not Enabled 4. Archive before truncation (-lgArchiveEnable): Not Enabled 5. Truncation frequency (-lgTruncateFrequency): Not Enabled 6. Maximum size before truncation (-lgTruncateSize): Not Enabled 7. Time of day for truncation (-lgTruncateTime): 00:00 + -nodupttidxerror + -perstrigfix + -zforceStart -evtlevel was temporary removed in 11.7.2 and 11.7.3 and added back in 11.7.3 -evtlevel https://knowledgebase.progress.com/articles/Article/P178277 11.7.4 as of Oct 9 2018 ------------------------ No changes 11.7.5 as of Jun 7 2019 ------------------------ + -defrdlogentrytypes + -defrdlogginglevel <0-???> + -defrdlognumlines + -zDontFlushErrors 12.0 as of Feb 22 2019 ---------------------- - -emptyFields introduced in 11.7.3 - -nodupttidxerror introduced in 11.7.3 - -noUnicodePrinters introduced in 11.1.0 - -soapServername introduced in 11.7.0 - -wsdlServername introduced in 11.7.0 but the -servername introduced in 11.7.0 exists in 12.0 + -baselob Starting LOB number for statistics range + -lobrangesize Number of LOBs included in statistics collection + -baseuserlob Starting LOB number per user for statistics range + -userlobrangesize Number of lobs per user included in statistics collection + -ttbaselob Starting LOB number for statistics range + -ttlobrangesize Number of LOBs included in statistics collection + -picanap Maximum nap time when blocked to access PICA queue Default: 1 ms + -retryAfterCatch Retry After Catch Reverts to the old behavior after an error is caught in a FOR EACH block [Client startup parameter] Since V12.0 the default action after an error is caught in a FOR EACH block will be NEXT. The old behavior is RETRY. + -ssj <0|1> Database server side join support [Login Broker] 0 — Server-side JOIN processing is disabled for this server. This is the default for a non-threaded database server. 1 — Server-side JOIN processing is enabled for this server. This is the default for a threaded database server. Server-side JOIN is only enabled for certain queries if the tables to be joined are in the same logical database and there are ten or fewer tables. For 12.0 Server-side JOIN is limited to queries that use NO-LOCK. The -ssj parameter is ignored if it's included in a server startup command with -threadedServer 0. + -threadedServer <0|1> Threaded Server [Login Broker] 0 indicates that servers spawned by the broker are not threaded. 1 indicates that the servers spawned by the broker are threaded. servers spawned by this database broker service remote client requests using individual threads, one thread per remote connection. The default is 1. + -threadedServerStack Threaded Server Stack [Login Broker] Specifys the size of a stack allocated for each thread spawned by a threaded server. + -zbdumpOE11enc + -zh - -m2 Manual Server + -zm2 Manual Server ?