OpenEdge Deployment: Startup Command and Parameter Reference

TM

2004 Progress Software Corporation. All rights reserved.

Progress software products are copyrighted and all rights are reserved by Progress Software Corporation. This manual is also copyrighted and all rights are reserved. This manual may not, in whole or in part, be copied, photocopied, translated, or reduced to any electronic medium or machine-readable form without prior consent, in writing, from Progress Software Corporation. The information in this manual is subject to change without notice, and Progress Software Corporation assumes no responsibility for any errors that may appear in this document. The references in this manual to specific platforms supported are subject to change. Allegrix, A [Stylized], ObjectStore, Progress, Powered by Progress, Progress Fast Track, Progress Profiles, Partners in Progress, Partners en Progress, Progress en Partners, Progress in Progress, P.I.P., Progress Results, ProVision, ProCare, ProtoSpeed, SmartBeans, SpeedScript, and WebSpeed are registered trademarks of Progress Software Corporation or one of its subsidiaries or affiliates in the U.S. and/or other countries. AccelEvent, A Data Center of Your Very Own, Allegrix & Design, AppsAlive, AppServer, ASPen, ASP-in-a-Box, BusinessEdge, Business Empowerment, Empowerment Center, eXcelon, Fathom, Future Proof, IntelliStream, ObjectCache, OpenEdge, PeerDirect, POSSE, POSSENET, ProDataSet, Progress Business Empowerment, Progress Dynamics, Progress Empowerment Center, Progress Empowerment Program, Progress for Partners, Progress OpenEdge, Progress Software Developers Network, PSE Pro, PS Select, Real Time Event Engine, SectorAlliance, SmartBrowser, SmartComponent, SmartDataBrowser, SmartDataObjects, SmartDataView, SmartDialog, SmartFolder, SmartFrame, SmartObjects, SmartPanel, SmartQuery, SmartViewer, SmartWindow, Technical Empowerment, Trading Accelerator, WebClient, and Who Makes Progress are trademarks or service marks of Progress Software Corporation or one of its subsidiaries or affiliates in the U.S. and other countries. SonicMQ is a registered trademark of Sonic Software Corporation in the U.S. and other countries. Vermont Views is a registered trademark of Vermont Creative Software in the U.S. and other countries. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Any other trademarks or service marks contained herein are the property of their respective owners. OpenEdge includes Imaging Technology copyrighted by Snowbound Software 1993-2003. www.snowbound.com. OpenEdge includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright 1999 The Apache Software Foundation. All rights reserved (Xerces C++ Parser (XML)) and Copyright 2000-2003 The Apache Software Foundation. All rights reserved (Ant). The names Apache, Xerces, ANT, and Apache Software Foundation must not be used to endorse or promote products derived from this software without prior written permission. Products derived from this software may not be called Apache, nor may Apache appear in their name, without prior written permission of the Apache Software Foundation. For written permission, please contact apache@apache.org. Software distributed on an AS IS basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License agreement that accompanies the product. OpenEdge includes software are copyrighted by DataDirect Technologies, 1991-2002. OpenEdge includes software developed by Vermont Creative Software. Copyright 1988-1991 by Vermont Creative Software. OpenEdge includes software developed by IBM and others. Copyright 1999, International Business Machines Corporation and others. All rights reserved. OpenEdge includes code licensed from RSA Security, Inc. Some portions licensed from IBM are available at http://oss.software.ibm.com/icu4j/. OpenEdge includes the UnixWare platform of Perl Runtime authored by Kiem-Phong Vo and David Korn. Copyright 1991, 1996 by AT&T Labs. Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the supporting documentation for such software. THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHORS NOR AT&T LABS MAKE ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. OpenEdge includes the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Copyright 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved. OpenEdge includes software developed by the World Wide Web Consortium. Copyright 1994-2002 World Wide Web Consortium, (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University). All rights reserved. This work is distributed under the W3C Software License [http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231] in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

August 2004

Product Code: 4653 Item Number: 101206; R10.0B

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface1 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the startup commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the startup parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using parameter files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calling parameter files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating and editing parameter files . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Startup and Shutdown Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Startup command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks you can perform with startup and shutdown commands . . . . . . . . . . . . . . . Startup and shutdown command descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . BPRO command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MBPRO command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MPRO command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PRO command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROAIW command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROAPW command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROBIW command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROBRKR command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROQUIET command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROSERVE command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROSHUT command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROWDOG command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROWIN32 command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 12 12 13 14 15 16 21 22 23 25 26 28 29 210 211 212 213 214 215 216 218 222 223

2.

Contents 3. Startup Parameter Usage Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the startup parameters and usage categories . . . . . . . . . . . . . . . . . . . . . . . Client Session parameters (CS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client performance parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client product-type parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Progress 4GL parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client internationalization parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . Session statistics parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows session parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Connection parameters (CC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client database connection parameters. . . . . . . . . . . . . . . . . . . . . . . . . . OpenEdge Database Server parameters (DBS) . . . . . . . . . . . . . . . . . . . . . . . . . . Database server performance parameters. . . . . . . . . . . . . . . . . . . . . . . . Database server-type parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database server internationalization parameters. . . . . . . . . . . . . . . . . . . Database server statistics collection parameters . . . . . . . . . . . . . . . . . . . Database server network parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . DataServer parameters (DS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Startup Parameter Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single-user Mode (-1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AdminServer Group (-admingroup) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AdminServer Port (-adminport) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . After-image Buffers (-aibufs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . After-image Stall (-aistall) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Async Queue Size (-asyncqueuesize) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blocks in Database Buffers (-B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Batch (-b) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ADE R-code Location (-baseADE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Index (-baseindex) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Registry Base Key (-basekey) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Table (-basetable) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before-image Buffers (-bibufs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Threshold Stall (-bistall) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovery Log Threshold (-bithold) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Private Read-only Buffers (-Bp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum Private Buffers per Connection (-Bpmax) . . . . . . . . . . . . . . . . . . . . . . . Bleeding Record Lock (-brl) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Buffer Size for Temporary Tables (-Bt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index Cursors (-c) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schema Cache File (-cache) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check Double-byte Enabled (-checkdbe) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check Width (-checkwidth) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Server Java Classpath (-classpath) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 32 32 33 34 35 38 310 311 312 312 315 315 318 318 319 320 322 41 42 43 44 45 46 47 48 49 410 412 413 414 415 416 417 418 419 420 421 422 423 425 426 427

4.

iv

Contents Client Logging (-clientlog) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conversion Map (-convmap) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communications Parameter File (-cp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case Table (-cpcase) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collation Table (-cpcoll) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal Code Page (-cpinternal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log File Code Page (-cplog) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Print Code Page (-cpprint) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-code in Code Page (-cprcodein) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-code Out Code Page (-cprcodeout) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stream Code Page (-cpstream) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminal Code Page (-cpterm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cursor Size (-cs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directory Size (-D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Date Format (-d) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataService (-DataService) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical Database Name (-db) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Debugger (-debug) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Debug Alert (-debugalert) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Attachable Debugging (-debugReady) . . . . . . . . . . . . . . . . . . . . . . . . . . . Dictionary Expressions (-dictexps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Direct I/O (-directio) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataServer (-Dsrv) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Type (-dt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . European Numeric Format (-E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Level (-evtlevel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expand Browse (-expandbrow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Force Access (-F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schema Field Cache Size (-fc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering Asynchronous COM Events (-filterocxevents) . . . . . . . . . . . . . . . . . . . . . Field List Disable (-fldisable) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before-image Cluster Age (-G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Group Delay (-groupdelay) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Host Name (-H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of Databases (-h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardlimit (-hardlimit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hash Table Entries (-hash) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No Crash Protection (-i) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamics Parameter (-icfparam) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index Range Size (-indexrangesize) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initialization File (-ininame) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input Characters (-inp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AS/400 Ignore Stamp (-is) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial Value Segment No Convert (-isnoconv) . . . . . . . . . . . . . . . . . . . . . . . . . . . Keyword Forget List (-k) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 469 470 471 472 473 474 475 v

Contents Key Alias (-keyalias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key Alias Password (-keyaliaspasswd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lock Table Entries (-L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local Buffer Size (-l) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Database Name (-ld) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lock Timeout (-lkwtmo) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Language (-lng) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log Entry Types (-logentrytypes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging Level (-logginglevel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log Threshold (-logthreshold) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auto Server (-m1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual Server (-m2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Secondary Login Broker (-m3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum Clients Per Server (-Ma) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum Dynamic Server (-maxport) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delayed BI File Write (-Mf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Minimum Clients per Server (-Mi) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Minimum Dynamic Server (-minport) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Buffer Size (-Mm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum Memory (-mmax) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum Servers (-Mn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Servers Per Protocol (-Mp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum Servers Per Broker (-Mpb) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VLM Page Table Entry Optimization (-Mpte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Record Buffer Size (-Mr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shared-memory Overflow Size (-Mxs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of Users (-n) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Nested Blocks (-nb) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No Lock (-NL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No Auto Result-list (-noautoreslist) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No Check Temp-table Names (-nochkttnames) . . . . . . . . . . . . . . . . . . . . . . . . . . . No Host Verify (-nohostverify) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index Hint (-noindexhint) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Join (-nojoinbysqldb) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No Session Cache (-nosessioncache) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No Session Reuse (-nosessionreuse) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SELECT Pass Through Disable (-noSQLbyserver) . . . . . . . . . . . . . . . . . . . . . . . . Fractional Separator (-numdec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of Log Files to Keep (-numlogfiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Thousands Separator (-numsep) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer (-o) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outer-join Mode (-ojmode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Password (-P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Startup Procedure (-p) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter (-param) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi 476 477 478 479 480 481 482 483 487 489 491 492 493 494 495 496 497 498 499 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4123 4124 4125 4126

Contents Pending Connection Time (-PendConnTime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter File (-pf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pin Shared Memory (-pinshm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROLIB Memory (-plm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROLIB Swap (-pls) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fast Schema Change (-populate) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Properties File (-properties) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Proxy Host (-proxyhost) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Proxy Password (-proxyPassword) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Proxy Port (-proxyport) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Proxy Userid (-proxyUserid) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Quick Request (-q) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-reliable I/O (-r) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alternate Random Number Generator (-rand) . . . . . . . . . . . . . . . . . . . . . . . . . . . Reread Nolock (-rereadnolock) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Run 4GL Client (-rg) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Read-only Media (-RO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Run Query Client (-rq) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Run Run-time Client (-rr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encrypted Compiler Mode (-rx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Name (-S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stack Size (-s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Semaphore Sets (-semsets) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Group (-servergroup) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Type of Server to Start (-ServerType) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Session Timeout (-sessiontimeout) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AS/400 Server Program Name (-Sn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Spin Lock Retries (-spin) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Open Cursors (-SQLCursors) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Stack Size (-SQLStack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Statement Cache Size (-SQLStmtCache) . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Sorting Memory (-SQLTempBuff) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Sorting on Disk (-SQLTempDisk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL Temp Table Data Page (-SQLTempPgSize) . . . . . . . . . . . . . . . . . . . . . . . . . SSL-based Connection (-ssl) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stash Area (-stsh) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Temporary Directory (-T) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Save Temp Files (-t) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table Range Size (-tablerangesize) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Speed Sort (-TB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Merge Number (-TM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Token (-tok) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trigger Location (-trig) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User ID (-U) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use OS Locale (-useOsLocale) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4143 4144 4145 4146 4147 4148 4150 4151 4152 4153 4154 4155 4156 4158 4159 4160 4161 4162 4163 4164 4165 4166 4168 4169 4170 4171 4172 4173 4174 4175 vii

Contents Version 6 Colon (-v6colon) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version 6 Query (-v6q) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows Passthrough Printing (-Wa -wpp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows Single Session (-wss) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows Exit - No Dialog (-wy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics (-y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics with CTRL-C (-yc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Segment Statistics (-yd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Four Digit Year Default (-yr4def) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics With Cross-reference (-yx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Century Year Offset (-yy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4176 4177 4178 4179 4180 4181 4183 4184 4185 4186 4188 Index1

viii

Contents Tables Table 11: Table 21: Table 22: Table 23: Table 31: Table 32: Table 33: Table 34: Table 35: Table 36: Table 37: Table 38: Table 39: Table 310: Table 311: Table 312: Table 313: Table 314: Table 41: Table 42: Table 43: Table 44: Table 45: Control characters in parameter files . . . . . . . . . . . . . . . . . . . . . . . . . . OpenEdge command components . . . . . . . . . . . . . . . . . . . . . . . . . . . UNIX and Windows startup and shutdown commands . . . . . . . . . . . . Windows-only startup commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . Startup parameter usage categories . . . . . . . . . . . . . . . . . . . . . . . . . . Client performance parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client product-type parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client 4GL parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client internationalization parameters . . . . . . . . . . . . . . . . . . . . . . . . . Session statistics parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows session parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client database connection parameters . . . . . . . . . . . . . . . . . . . . . . . Server performance parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server-type parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server internationalization parameters . . . . . . . . . . . . . . . . . . . . . . . . Server statistics collection parameters . . . . . . . . . . . . . . . . . . . . . . . . Server network parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataServer parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log entry types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter interpretation with Service Name (-S) . . . . . . . . . . . . . . . . Attributes set by Use OS Locale (useOsLocale) . . . . . . . . . . . . . . . . Century setting and date format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 22 23 24 32 33 34 35 38 310 311 312 315 318 318 319 320 322 484 487 4149 4175 4188

ix

Contents

Preface
This Preface contains the following sections: Purpose Audience Organization Using this manual Typographical conventions Examples of syntax descriptions OpenEdge messages

OpenEdge Deployment: Startup Command and Parameter Reference

Purpose
This book provides business application developers and system administrators for OpenEdge with a comprehensive reference of the startup and shutdown commands and the startup parameters.

Audience
The primary audiences for this book are business application developers and OpenEdge system administrators. The secondary audiences are OpenEdge developers and technical support engineers.

Organization
Chapter 1, Introduction Introduces the startup commands and parameters. Chapter 2, Startup and Shutdown Commands Describes the OpenEdge commands for starting up and shutting down OpenEdge sessions and processes. Chapter 3, Startup Parameter Usage Categories Provides an overview of the OpenEdge startup parameters organized by usage category. Chapter 4, Startup Parameter Descriptions Describes the OpenEdge startup parameters in detail, in alphabetical order by syntax.

Using this manual

Use the introductory material in Chapters 1, 2, and 3 to become familiar in general with the commands and parameters. Then use the quick reference tables in Chapters 2 and 3 to find the command or parameter that you need. If you need additional information about a parameter, refer to the descriptions in Chapter 4.

Preface2

Preface

Typographical conventions
This manual uses the following typographical conventions:

Convention Bold Italic

SMALL, BOLD CAPITAL LETTERS KEY1-KEY2

Description Bold typeface indicates commands or characters the user types, or the names of user interface elements. Italic typeface indicates the title of a document, provides emphasis, or signifies new terms. Small, bold capital letters indicate OpenEdge key functions and generic keyboard keys; for example, GET and CTRL. A hyphen between key names indicates a simultaneous key sequence: you press and hold down the first key while pressing the second key. For example, CTRL-X. A space between key names indicates a sequential key sequence: you press and release the first key, then press another key. For example, ESCAPE H.

KEY1 KEY2

Syntax:
Fixed width

A fixed-width font is used in syntax statements, code examples, and for system output and filenames. Fixed-width italics indicate variables in syntax statements. Fixed-width bold indicates variables with special emphasis. Uppercase words are Progress 4GL language keywords. Although these always are shown in uppercase, you can type them in either uppercase or lowercase in a procedure. This icon (three arrows) introduces a multi-step procedure. This icon (one arrow) introduces a single-step procedure.

Fixed-width italics Fixed-width bold UPPERCASE fixed width

Period (.) or colon (:)

All statements except DO, FOR, FUNCTION, PROCEDURE, and REPEAT end with a period. DO, FOR, FUNCTION, PROCEDURE, and REPEAT statements can end with either a period or a colon.

Preface3

OpenEdge Deployment: Startup Command and Parameter Reference

Convention

Description Large brackets indicate the items within them are optional. Small brackets are part of the Progress 4GL language. Large braces indicate the items within them are required. They are used to simplify complex syntax diagrams. Small braces are part of the Progress 4GL language. For example, a called external procedure must use braces when referencing arguments passed by a calling procedure. A vertical bar indicates a choice. Ellipses indicate repetition: you can choose one or more of the preceding items.

[]
[]

{}
{}

| ...

Examples of syntax descriptions

In this example, ACCUM is a keyword, and aggregate and expression are variables: Syntax
ACCUM aggregate expression FOR

is one of the statements that can end with either a period or a colon, as in this example:

FOR EACH Customer: DISPLAY Name. END.

In this example, STREAM stream, UNLESS-HIDDEN, and NO-ERROR are optional: Syntax
DISPLAY

STREAM stream

][

UNLESS-HIDDEN

] [

NO-ERROR

Preface4

Preface In this example, the outer (small) brackets are part of the language, and the inner (large) brackets denote an optional item: Syntax
INITIAL [ constant

, constant

A called external procedure must use braces when referencing compile-time arguments passed by a calling procedure, as shown in this example: Syntax
{ &argument-name }

In this example, EACH, FIRST, and LAST are optional, but you can choose only one of them: Syntax
PRESELECT

EACH

FIRST

LAST

record-phrase

In this example, you must include two expressions, and optionally you can include more. Multiple expressions are separated by commas: Syntax
MAXIMUM ( expression , expression

, expression

] ...

In this example, you must specify MESSAGE and at least one expression or SKIP [ (n) any number of additional expression or SKIP [ ( n ) Syntax
MESSAGE

], and

] is allowed:

expression

SKIP

( n )

] } ...

Preface5

OpenEdge Deployment: Startup Command and Parameter Reference In this example, you must specify {include-file, then optionally any number of argument or &argument-name = "argument-value", and then terminate with }: Syntax
{ include-file

argument

&argument-name = "argument-value"

] ...

Long syntax descriptions split across lines

Some syntax descriptions are too long to fit on one line. When syntax descriptions are split across multiple lines, groups of optional and groups of required items are kept together in the required order. In this example, WITH is followed by six optional items: Syntax
WITH

ACCUM max-length

][

expression DOWN

[ [

CENTERED

STREAM-IO

] [ ]

n COLUMNS

][

SIDE-LABELS

] ]

Complex syntax descriptions with both required and optional elements

Some syntax descriptions are too complex to distinguish required and optional elements by bracketing only the optional elements. For such syntax, the descriptions include both braces (for required elements) and brackets (for optional elements). In this example, ASSIGN requires either one or more field entries or one record. Options available with field or record are grouped with braces and brackets: Syntax
ASSIGN

{ [ FRAME frame ] { field [ = expression ] } [ WHEN expression ] } ... | { record [ EXCEPT field ... ] }

Preface6

Preface

OpenEdge messages
OpenEdge displays several types of messages to inform you of routine and unusual occurrences: Execution messages inform you of errors encountered while OpenEdge is running a procedure; for example, if OpenEdge cannot find a record with a specified index field value. Compile messages inform you of errors found while OpenEdge is reading and analyzing a procedure before running it; for example, if a procedure references a table name that is not defined in the database. Startup messages inform you of unusual conditions detected while OpenEdge is getting ready to execute; for example, if you entered an invalid startup parameter.

After displaying a message, OpenEdge proceeds in one of several ways: Continues execution, subject to the error-processing actions that you specify or that are assumed as part of the procedure. This is the most common action taken after execution messages. Returns to the Progress Procedure Editor, so you can correct an error in a procedure. This is the usual action taken after compiler messages. Halts processing of a procedure and returns immediately to the Progress Procedure Editor. This does not happen often. Terminates the current session.

OpenEdge messages end with a message number in parentheses. In this example, the message number is 200:

** Unknown table name table. (200)

If you encounter an error that terminates OpenEdge, note the message number before restarting.

Preface7

OpenEdge Deployment: Startup Command and Parameter Reference

Obtaining more information about OpenEdge messages

On Windows platforms, use OpenEdge online help to obtain more information about OpenEdge messages. Many OpenEdge tools include the following Help menu options to provide information about messages: Choose HelpRecent Messages to display detailed descriptions of the most recent OpenEdge message and all other messages returned in the current session. Choose HelpMessages and then enter the message number to display a description of a specific OpenEdge message. In the Progress Procedure Editor, press the HELP key or F1.

On UNIX platforms, use the Progress pro command to start a single-user mode character OpenEdge client session and view a brief description of a message by providing its number. To use the pro command to obtain a message description by message number: 1. Start the Progress Procedure Editor:

install-dir/dlc/bin/pro

2. 3. 4.

Press F3 to access the menu bar, then choose Help Messages. Type the message number and press ENTER. Details about that message number appear. Press F4 to close the message, press F3 to access the Progress Procedure Editor menu, and choose File Exit.

Preface8

1
Introduction
This chapter introduces the commands and parameters you can use to start up and shut down OpenEdge processes. It also describes how to use a parameter file (.pf) to maintain startup parameters for a particular database startup, client session startup, or database connection. The following topics are included: About the startup commands About the startup parameters Using parameter files

OpenEdge Deployment: Startup Command and Parameter Reference

About the startup commands

OpenEdge provides startup commands that support its client/server architecture and a wide range of configuration options. In client/server configurations, the client application and database server are separate processes. The OpenEdge user interface and OpenEdge applications execute in a client session, sending requests to the OpenEdge server. The OpenEdge server accesses the database on behalf of each client session. Consequently, the startup commands fall into two general categories: Commands to startup and shutdown database processes, such as database servers, database brokers, and background writer. Commands to start up and shutdown client sessions that connect to databases, such as a 4GL client, AppServer, and DataServer client.

After setting up your database, you are ready to run OpenEdge. In general, you start clients and servers as follows: Start a database server or broker for a database. Starting a server or broker for a database is distinct from connecting to a database. For more information on starting these processes, see OpenEdge Getting Started: Installation and Configuration for UNIX or OpenEdge Getting Started: Installation and Configuration for Windows. Start the client applications.

For more information about the startup commands, see Chapter 2, Startup and Shutdown Commands.

About the startup parameters

You use startup parameters with the startup commands to help define the context in which the database processes and client sessions run. The requirements and use of parameters varies with the different operating systems and network environments. For example, you can use the startup parameters to control how a client connects to a database and enhance database server and client performance. These parameters are organized into the following usage categories: 12 Client session Client connection OpenEdge database server

Introduction DataServer Open interface driver

For information about the startup parameter usage categories, see Chapter 3, Startup Parameter Usage Categories. For details about each parameter, see Chapter 4, Startup Parameter Descriptions. You can access the list of startup parameters defined at startup for the current OpenEdge session by reading the STARTUP-PARAMETERS attribute on the SESSION system handle from a 4GL procedure. For more information about the STARTUP-PARAMETERS attribute, or the SESSION system handle, see the OpenEdge Development: Progress 4GL Reference.

Using parameter files

A parameter file is an operating system file that contains one or more startup parameters. The primary reason to use a parameter file is to avoid typing commands each time you want to start OpenEdge. Instead of repeatedly typing a series of parameters and other arguments, type them once and place them in a parameter file. You also can use a parameter file to maintain the startup parameters for a particular database, group of users, or system configuration. A parameter file has a .pf extension. Every OpenEdge executable invokes a parameter file named startup.pf by default. This file is located in the DLC directory. It must exist for OpenEdge to execute properly. You can modify startup.pf to add parameter definitions. You can also create one or more additional parameter files and direct OpenEdge to invoke them after it invokes startup.pf. Note: In Windows, you can specify the name of the OpenEdge startup file using the PROSTARTUP environment variable in the progress.ini file and the Registry. See OpenEdge Deployment: Managing 4GL Applications for more information on the progress.ini file.

13

OpenEdge Deployment: Startup Command and Parameter Reference

Calling parameter files

To call an additional parameter file, use the Parameter File (-pf) startup parameter in the OpenEdge startup command line or in a CONNECT statement. Calling a parameter file in a startup command From a startup command line, use the Parameter File (-pf) startup parameter to call the parameter file. Enter one of the following commands:

Operating system UNIX Windows

Syntax
pro sports -pf filename.pf prowin32 -1 sports -pf filename.pf

(Specify in the Command Line field of a Shortcut Properties dialog box.) The filename can be any valid filename. OpenEdge combines all parameters on a command line with those in the parameter file. If the same parameter is mentioned more than once, the last occurrence takes precedence. For more information on startup parameters, see Chapter 3, Startup Parameter Usage Categoriesand Chapter 4, Startup Parameter Descriptions. Calling a parameter file in a CONNECT statement Use the following syntax to specify a parameter file in a CONNECT statement in a Progress 4GL procedure:

CONNECT -pf sports.pf

For example, this procedure connects using a parameter file called new_york.pf: new_york.p
UPDATE ny_user ny_password BLANK. CONNECT -pf new_york.pf -U VALUE(ny_user) -P VALUE(ny_passwd) NO-ERROR. IF NOT CONNECTED("new_york") THEN MESSAGE "Connection to New York office failed".

14

Introduction Calling multiple parameter files You can use the -pf parameter as many times as you like on a command line. This lets you specify application-specific parameters in one parameter file, database-specific parameters in a second parameter file, and user-specific parameters in yet another parameter file. It also allows you to connect to multiple databases from the same command line or CONNECT statement. When connecting to more than one database, the startup parameters must appear after the corresponding Physical Database Name (-db) parameter and database name. If connecting to more than one database, consider putting all the database-related parameters in a parameter file, then add the -db parameter to the top of the file. To support earlier releases, OpenEdge assigns any startup parameters that precede all database names to the first database on the command line. OpenEdge processes parameters from left to right. Each -pf parameter encountered is processed first before the next top-level parameter is evaluated. If a parameter file specified by -pf contains another -pf parameter, the nested parameter file is evaluated before resuming the top-level processing. Note: If the same parameter is mentioned more than once, the last occurrence takes precedence.

Creating and editing parameter files

You can use any text editor to create a file containing startup parameters. Follow the format explained in the Parameter file format section on page 16. You also can use OpenEdge tools to create and edit parameter files. To create and edit parameter files: 1. 2. Access the Data Administration tool or Data Dictionary. Choose UtilitiesEditor for Parameter Files. OpenEdge prompts you for the file you want to create or edit. Specify the filename. OpenEdge alphabetically lists all available startup parameters.

3.

15

OpenEdge Deployment: Startup Command and Parameter Reference 4. Specify which of the parameters you want in the file by choosing the parameter and entering yes, no, or the appropriate value. Enter any comments you want to include in the parameter file. After creating the parameter file, OpenEdge returns you to the Data Administration or Data Dictionary main window.

5.

Parameter file format

The following is a sample parameter file: new_york.pf
-db -B -H -L # /usr/disk0/newyork 200 nysystem -S nyserver 10000 # new york central db # database buffers # host, service # lock table entries

All other parameters receive their default values.

16

Introduction The format of the parameter file is the same for all operating systems. Follow these rules when creating a parameter file: Place a parameter and its argument on the same line. Use a maximum of 40 tokens per line in a parameter file. Specify parameters with the UNIX syntax. Use a pound sign (#) to begin a comment. OpenEdge ignores the rest of the line. Enclose a value in single () or double () quotes. Any white space inside the quotes is treated as part of the token. Any parameter not named in a parameter file receives a default value. To remind yourself of the default values, consider specifying all parameters and their values in the parameter file and adding the comment # default to those values that do not change. Use a tilde (~) to suppress the special meaning of the single () or double () quotes or tilde (~). A tilde also prefixes the control characters listed in Table 11 that OpenEdge can recognize in a parameter file. Control characters in parameter files Description The character having octal code nnn BS character HT (horizontal tab) character LF (line feed) character VT (carriage return) character FF (form feed) character ESC character ~010 ~011 ~012 ~013 ~014 ~033 Octal code

Table 11: Character ~nnn ~b ~t ~n ~r ~f ~E

On UNIX, use the backslash (\) in place of a tilde.

17

OpenEdge Deployment: Startup Command and Parameter Reference

18

2
Startup and Shutdown Commands
This chapter presents the OpenEdge startup and shutdown commands that you can enter at the command line. It describes the syntax of a startup command, summarizes the tasks you can perform with startup commands, and then describes each command and its parameters. For more information on how parameters are used, see Chapter 3, Startup Parameter Usage Categories. For details on each parameter, see Chapter 4, Startup Parameter Descriptions.

Startup command syntax

Startup command syntax

These are the conventions used in command syntax descriptions:

command

db-name

][

parameter

] [

value

] ...

For example, you can use the following command to allow 100 users to access the sports database and then set values for the database connection, performance, and network parameters:

proserve sports -n 100 -B 30000 -L 1000 -S sprtsv -H sys27

Table 21 describes each command component. Table 21: Component

command

OpenEdge command components Description On UNIX, the command runs a script that executes an OpenEdge executable with appropriate parameters. On Windows, some commands run a batch file that executes an OpenEdge executable with appropriate parameters. Other commands run an OpenEdge executable directly.

db-name parameter value

Name of the database to which you want to connect. Operating criteria for the command. Numeric value or file specification for the parameter.

Observe the following conventions when entering a command: On UNIX, commands are lowercase. On Windows, commands are not case sensitive. On UNIX and Windows, enter parameters exactly as shown in the syntax descriptions. On UNIX, values can be case sensitive; for example, UNIX filenames are case sensitive. In addition, on Windows NT using the NT File System (NTFS), values can be case sensitive. On Windows using the File Allocation Table (FAT or FAT32) file system, values are not case sensitive.

22

Tasks you can perform with startup and shutdown commands

Tasks you can perform with startup and shutdown commands

Startup commands start up and shut down OpenEdge database or client processes. Table 22 summarizes the tasks you can perform on UNIX and Windows systems and the related startup and shutdown commands. Table 22: UNIX and Windows startup and shutdown commands Task Start a character Procedure Editor and connect to a single-user database. Start a character Procedure Editor and connect to a multi-user database Start an OpenEdge character client session in batch mode and connect to a single-user database. Start an OpenEdge character client session in batch mode and connect to a multi-user database. Start an OpenEdge server group. Start a server or broker for a multi-user OpenEdge database. Shut down a multi-user server or broker for an OpenEdge database. Start a remote OpenEdge DataServer broker. Start an asynchronous page writer (APW) for a database.1 Start a before-image writer (BIW).1 Start an after-image writer (AIW).1
pro db-name

(1 of 2)

Command

mpro db-name -S service-name -H host-name -N network-type bpro db-name -p procedure-name

mbpro db-name -p -S -H -N

procedure-name service-name host-name network-type

proserve -servergroup server-group-name proserve db-name -S service-name -H host-name -N network-type proshut db-name

probrkr -S service-name -H host-name proapw db-name

probiw db-name proaiw db-name

23

Tasks you can perform with startup and shutdown commands Table 22: UNIX and Windows startup and shutdown commands Task Start the OpenEdge Watchdog utility.1 Shut down a remote OpenEdge DataServer. Shut down an APW, AIW, BIW, or Watchdog process.1 Choose option 1 (Disconnect a User) to disconnect the process.
1

(2 of 2)

Command
prowdog db-name proshut db-name -S service-name -H host-name -N network-type proshut db-name

Option available only on Enterprise product

Table 23 summarizes tasks and their related startup commands for Windows only. You can use these commands in the Command Line field of a Shortcuts Properties dialog box. Table 23: Windows-only startup commands Task Start a GUI Procedure Editor and connect to a single-user database. Start a GUI Procedure Editor and connect to a multi-user database. Start the ADE Desktop and connect to a single-user database. Start the ADE Desktop and connect to a multi-user database. Start an OpenEdge batch session and connect to a single-user database. Start an OpenEdge batch session and connect to a multi-user database.
prowin32 -1 db-name

Command

prowin32 db-name -S service-name -H host-name -N network-type prowin32 -p _desk.p -1 db-name

prowin32 -p _desk.p -1 db-name -S service-name -H host-name -N network-type prowin32 -b -1 db-name -p procedure

prowin32 -b -p -S -H -N

db-name procedure service-name host-name network-type

24

Startup and shutdown command descriptions

Startup and shutdown command descriptions

The following sections describe the OpenEdge startup commands in detail, in alphabetical order. Each section includes a table that shows the syntax of the command and other information about it. Following the table is a description of each parameter. Note: In general, if the database is not in your current directory, you must specify the full pathname of the database. There are a few exceptions. See the description of the command you want to use for more information.

25

BPRO command

BPRO command
Starts a single-user OpenEdge client session in batch or background mode. Syntax Operating system UNIX Windows
bpro [ db-name

Syntax

-p procedure-name

[ parameters ]

[>

output-file

Parameters

db-name

Specifies the database you want to connect.

-p procedure-name

Specifies a procedure to run at startup.

parameters

Specifies the OpenEdge startup parameters you want to use.

output-file

Specifies the name of the file where messages are sent.

26

BPRO command Notes For UNIX, the BPRO command runs the following executable:

_progres -1 -b &

The & character causes an OpenEdge batch session to run in the background, and returns control to the terminal once the session starts. When the & character is not present (for example, when you simply use the (-b) startup parameter), OpenEdge initiates a batch session in the foreground without terminal interaction and control does not return to the terminal until the session completes. On UNIX and Windows NT, you can redirect batch job input and output with the < and > redirection symbols. You also can use the pipe symbol (|) to put an OpenEdge batch run in a command pipeline.

27

MBPRO command

MBPRO command
Starts a multi-user OpenEdge client session in batch or background mode. Syntax Operating system UNIX Windows
mbpro

Syntax

[ [

db-name

-p procedure-name

parameters

] [

> output-file

Parameters

db-name

Specifies the database you want to connect. If you are connecting to a database through shared memory and the database is not in your current directory, you must specify the path of the database. On the other hand, if you are making a client/server connection to the database, you do not need to specify a path.
-p procedure-name

Specifies the procedure to run at startup.

parameters

Specifies the startup parameters you want to use.

output-file

Specifies a file where output messages are sent. Notes On UNIX, the MBPRO command runs the following executable:

_progres -b &

On UNIX and Windows NT, you can redirect batch job input and output with the < and > redirection symbols. You also can use the pipe symbol (|) to put an OpenEdge batch run in a command pipeline.

28

MPRO command

MPRO command
Starts a multi-user mode character OpenEdge client session. Syntax Operating system UNIX Windows Parameters
db-name mpro

Syntax

db-name

] [

parameters

Specifies the database to which you want to connect. If you are connecting to a database through shared memory and the database is not in your current directory, you must specify the path of the database. On the other hand, if you are making a client/server connection to the database, you do not need to specify a path.
parameters

Specifies the startup parameters you want to use. Notes The MPRO command runs the following executable:

_progres

The server must be running before you issue this command with the db-name parameter. If the server is not running, OpenEdge displays the following error message:

There is no server for database db-name (1423)

29

PRO command

PRO command
Starts a single-user mode character OpenEdge client session. Syntax Operating system UNIX Windows Parameters
db-name pro

Syntax

db-name

] [

parameters

Specifies the database you want to start.

parameters

Specifies the parameters you want to use. You can use any single-user startup parameter with the PRO command. Note The PRO command runs the following executable:

_progres -1

210

PROAIW command

PROAIW command
Starts the after-image writer (AIW) process. The AIW improves performance on shared-memory systems by performing overhead after-image operations in the background. For more information on the AIW, see OpenEdge Data Management: Database Administration. Syntax Operating system UNIX Windows Parameters
db-name proaiw db-name

Syntax

Specifies the database where you want to start the AIW process. Notes To stop the AIW, disconnect it by using the PROSHUT command. You can start and stop the AIW at any time without shutting down the database. The AIW counts as one user. You might have to increment the value of the Number of Users (-n) parameter to allow for the AIW; however, the AIW does not count as a licensed user. You can increase the number of buffers in the after-image buffer pool by using the After-image Buffers (-aibufs) parameter. Increasing the number of buffers when running an AIW increases the availability of empty buffers to client and server processes. Increasing the After-image Buffers parameter has no effect if the AIW is not running.

211

PROAPW command

PROAPW command
Starts an asynchronous page writer (APW). APWs improve database performance on shared-memory systems by performing overhead operations in the background. For more information on APWs, see OpenEdge Data Management: Database Administration. Syntax Operating system UNIX Windows Parameters
db-name proapw db-name

Syntax

Specifies the database where you want to start an APW. Notes To stop an APW, disconnect it by using the PROSHUT command. You can start and stop APWs at any time without shutting down the database. Each APW counts as a user. You might have to increase the value of the Number of Users (-n) parameter to allow for APWs; however, APWs do not count as licensed users. The optimal number depends on your application and environment. To start, use one page writer for each disk where the database resides. If this is insufficient, add more. For an application that performs many updates, start one APW for each disk containing your database, plus one additional APW. Applications that perform fewer changes to a database require fewer APWs.

212

PROBIW command

PROBIW command
Starts a before-image writer (BIW) process. The BIW improves database performance on shared-memory systems by performing before-image overhead operations in the background. For more information on the BIW, see OpenEdge Data Management: Database Administration. Syntax Operating system UNIX Windows Parameters
db-name probiw db-name

Syntax

Specifies the database where you want to start a BIW. Notes To stop the BIW process, disconnect it by using the PROSHUT command. You can start and stop the BIW at any time without shutting down the database. The BIW process counts as one user. You might have to increment the value of the Number of Users (-n) parameter to allow for the BIW; however, the BIW does not count as a licensed user. You can increase the number of before-image buffers with the Before-image Buffers (-bibufs) parameter. Increasing the number of buffers increases the availability of empty buffers to client and server processes.

213

PROBRKR command

PROBRKR command
Starts the DataServer broker, which is used when OpenEdge clients connect to non-OpenEdge databases. To use the DataServer from a remote client, you must first start the broker. Once you start the broker, it can receive the client requests and spawn the appropriate DataServer. Syntax Operating system UNIX Windows Parameters
db-name probrkr

Syntax

[db-name]

-S service-name

-H host-name

Specifies the name of the database to which you are connecting.

service-name

Specifies the name of the broker process on the host machine.

host-name

Specifies the name of the machine where the DataServer broker is installed. This parameter is required only on UNIX System V systems using the TLI network type. The default value is the current host. Notes You can use any startup parameter with the PROBRKR command. For information about connecting to a non-OpenEdge database, remotely or locally, see the DataServer documentation. You must start the remote broker in the same environment where the non-OpenEdge database is, because the servers it spawns inherit the setup of the environment from the broker. For example, if you use an ORACLE database on a UNIX platform, set the ORACLE_SID value for that environment, as you would for a local DataServer. Start the broker on a node that is locally connected to the disk containing the non-OpenEdge database.

214

PROQUIET command

PROQUIET command
Stops all writes to database files by enabling a quiet processing point (useful for advanced backup strategies). You can also use the PROQUIET command with the bithreshold parameter to adjust the size of the recovery log threshold online. Use the -bithold startup parameter to set the size of the recovery log threshold on startup. For more information on using database quiet points, see OpenEdge Data Management: Database Administration. Syntax Operating system UNIX Windows
proquiet db-name -C

Syntax

{ {

enable

disable

} |

bithreshold n

Parameters

db-name

Specifies the name of the database where you are enabling or disabling a quiet processing point.
-C

Specifies a parameter.
enable | disable

Enables or disables a quiet processing point. Any processes that attempt transactions while a quiet point is enabled must wait until the quiet point is disabled.
bithreshold n

Specifies the maximum size to which .bi recovery files can grow, where n is an integer specifying the size of the threshold in MB. You can increase the size of the threshold above the current value or reduce the size to one cluster larger than the size of the recovery log file when the PROQUIET command is issued. You must issue the PROQUIET enable command to enable a quiet point before using the -bithreshold parameter to adjust the size of the threshold.

215

PROSERVE command

PROSERVE command
Starts the initial OpenEdge multi-user server process. This server process coordinates all access to the specified OpenEdge database. Syntax Operating system UNIX Windows
proserve

Syntax

{ [

db-name

-servergroup servergroup-name

parameters

Parameters

db-name

Specifies the specific database against which you want to start OpenEdge.
-servergroup servergroup-name

Specifies the logical collection of server processes to start. The servergroup-name you specify must match the name of a server group in the conmgr.properties file. You create server groups using the Progress Explorer tool, which saves them in the conmgr.properties file. For more information, see OpenEdge Getting Started: Installation and Configuration for Windows or OpenEdge Getting Started: Installation and Configuration for UNIX.
parameters

Specifies the startup parameters for the broker/server. If both -servergroup and parameters are specified, those that occur last on the command line take precedence. Notes The PROSERVE command runs the following executable:

_mprosrv

The initial database server process is called the broker. The process manages shared resources and starts servers for remote users, if necessary. You can specify only one database name when using PROSERVE to start a server or server group.

216

PROSERVE command Server groups manage network connections four separate ways: Accept no network connections. Accept SQL and 4GL network connections. Accept only SQL network connections. Accept only 4GL network connections.

Typically, server groups share common attributes such as connection port, number of servers, and how connected clients are distributed among the servers. You create server groups using the Progress Explorer tool, which saves them in the file. The servergroup-name you specify with the PROSERVE -servergroup parameter must match the name of a server group in the conmgr.properties file. Do not edit the conmgr.properties file directly; instead, use Progress Explorer.
conmgr.properties

The behavior of the -servergroup parameter is similar to the behavior of the -pf (parameter file) parameter. In effect, -servergroup causes a server to load the parameters associated with the server group, including the database name. It is possible to override the parameter values associated with a server group by adding additional parameters to the PROSERVE command. For example, if the database buffer pool is set to 10,000 within the configuration associated with a server group, you can specify a larger value by adding an additional parameter:

proserve -servergroup sports2000.myconfig.4GLdefault -B 20000

Conversely, if you specify a startup parameter before the -servergroup parameter, the startup parameter can be overridden when the same parameter is set in the server group configuration file. For example, if you place the additional parameter before the -servergroup parameter, the database buffer pool remains 10,000:

proserve -B 20000 -servergroup sports2000.myconfig.4GLdefault

217

PROSHUT command

PROSHUT command
Shuts down the OpenEdge database server and individual OpenEdge processes. Before you shut down the server, have all application users quit their OpenEdge sessions. If necessary, you can disconnect users by using the PROSHUT commands Disconnect a User or Unconditional Shutdown parameters. Syntax Operating system UNIX Windows
proshut db-name

Syntax

[ -b | -by | -bn | -C list | -C disconnect usernum | -cpinternal codepage | -cpstream codepage | -F | -Gw | -H host-name | -N network-type | -S service-nam ] ...

Parameters

db-name

Specifies the database against which the server is running.

-b

Directs OpenEdge to perform a batch shutdown. When no client is connected, the database automatically shuts down. When one or more clients are connected, PROSHUT prompts the user to enter yes to perform an unconditional batch shutdown and to disconnect all active users; or no to perform a batch shutdown only if there are no active users. The -b parameter combines the functionality of the -by or -bn parameters.
-by

Directs OpenEdge to perform an unconditional batch shutdown and to disconnect all active users. Using -by in conjunction with -F causes an emergency shutdown.

218

PROSHUT command
-bn

Directs OpenEdge to perform a batch shutdown only if there are no active users.
-C list

Lists all of the users connected to the database. The list is printed out to the screen without any page breaks.
-C disconnect usernum

Allows you to initiate a disconnect for the specified user. This is similar to option 1 of the PROSHUT menu.
-cpinternal codepage

Identifies the code page that OpenEdge uses in memory.

-cpstream codepage

Identifies the code page used for stream I/O.

-F

Starts an emergency shutdown. To use this parameter, you must run PROSHUT on the machine where the server resides. This parameter is not applicable for remote shutdowns or DataServer shutdowns.
-Gw

For DataServers, specifies the DataServer broker to shut down.

-H host-name

Specifies the machine where the database server runs. You must specify the host name if you issue the shutdown command from a machine other than the host.
-N network-type

Specifies the networking protocol used to connect to the database server. You must specify the network type if you issue the shutdown command from a machine other than the host.
-S service-name

Specifies the database server or broker process. You must specify the service name if you issue the shutdown command from a machine other than the host.

219

PROSHUT command When you enter the PROSHUT command without the -by, -bn, or -F parameters, the following menu appears:

1 2 3 x

Disconnect a User Unconditional Shutdown Emergency Shutdown (Kill All) Exit

The following table lists the menu options and their actions:

Option 1 2 3

Action Prompts you for the number of the user you want to disconnect. Disconnects all users and shuts down the database. Prompts you to confirm your choice. If you cancel the choice, you cancel the shutdown. If you confirm the choice, OpenEdge displays the following message:
Emergency shutdown initiated... PROSHUT

marks the database for abnormal shutdown, kills all remaining processes connected to the database, and deletes shared-memory segments and semaphores. The database is in a crashed state. OpenEdge performs normal crash recovery when you restart the database and backs out any active transactions.

Cancels the shutdown without taking any action.

220

PROSHUT command Notes The PROSHUT command runs the following executable:

_mprshut

You can access PROSHUT from the PROMON utility by using the Shut Down Database qualifier. The user who shuts down the server must have started it, or be root (on UNIX). When you initiate PROSHUT over a network, the amount of time that it takes to actually shut down all of the OpenEdge processes and to free any ports varies depending on the number of clients, brokers, and servers that must be shut down. The PROSHUT utility might return control to the terminal before all of the processes are stopped and resources are freed. If you specified a new value for -cpinternal or -cpstream when you opened the database, you must specify that same value for -cpinternal or -cpstream when you close the database with the PROSHUT command. If you do not, PROSHUT uses the values for -cpinternal and -cpstream found in the main startup parameter file created during installation (such as DLC/startup.pf). If the values of -cpinternal or -cpstream specified for your database do not match the values specified in the main startup parameter file, you receive the following error message:

Code page conversion table for table-name to table-name was not found. (6063)

221

PROWDOG command

PROWDOG command
Starts the OpenEdge Watchdog process. The Watchdog cleans up after improperly terminated OpenEdge processes. For example, it releases any locks or shared-memory structures that those processes might hold. Syntax Operating system UNIX Windows Parameters
db-name prowdog db-name

Syntax

Specifies the database to clean up after. Notes If the Watchdog finds a process that is no longer active, it releases all the appropriate record locks, backs out any live transactions, releases any shared-memory locks, and closes the connection. If the lost process is a server, it disconnects and cleans up all appropriate remote clients. If the process was changing shared memory when it terminated, shared memory is in an inconsistent state; the Watchdog forces a shutdown to protect the database. The Watchdog cannot detect lost remote clients because remote clients are not associated with a process. Instead, a network protocol timeout mechanism notifies the server that the network connection was lost.

222

PROWIN32 command

PROWIN32 command
Starts a graphical OpenEdge session. Syntax Operating system Windows Parameters
db-name prowin32

Syntax

db-name

] [

parameters

Specifies the database you are using.

parameters

Specifies the session or connection parameters you want to use. Note See OpenEdge Deployment: Managing 4GL Applications for more information about starting OpenEdge sessions and connecting to databases.

223

PROWIN32 command

224

3
Startup Parameter Usage Categories
This chapter provides an overview of the OpenEdge startup parameters organized by usage categories. The chapter includes the following topics: About the startup parameters and usage categories Client Session parameters (CS) Client Connection parameters (CC) OpenEdge Database Server parameters (DBS) DataServer parameters (DS)

Use this chapter as a quick reference. For a complete description of each startup parameter, listed in alphabetical order, see Chapter 4, Startup Parameter Descriptions.

About the startup parameters and usage categories

About the startup parameters and usage categories

You can change the default startup parameters by using startup parameters on a command line or by incorporating them into a .BAT file or a UNIX script file. You also can use an OpenEdge parameter file, which can include any number of startup parameters. See Chapter 1, Introduction for information on the parameter file. In this chapter, the startup parameters are organized into usage categories. Some parameters might be listed in multiple categories. Unless noted otherwise, the syntax of the parameters is the same for UNIX and Windows. Table 31 defines the startup parameter usage categories. Table 31: Startup parameter usage categories Usage type Client Session (CS) Client Connection (CC) OpenEdge Database Server (DBS) DataServer (DS) Purpose Use when starting any client session. Use when connecting to a specific database. Use when starting a server or broker. Use when starting non-OpenEdge DataServers.

Client Session parameters (CS)

Use the Client Session parameters when starting a session for a 4GL client or an AppServer (as client). The parameters are organized alphabetically by syntax in the following subcategories: Client performance parameters Client product-type parameters Progress 4GL parameters Client internationalization parameters Session statistics parameters Windows session parameters

32

Client performance parameters

Client performance parameters

Use the parameters listed in Table 32 to control client performance. Table 32: Syntax
-asyncqueuesize n

Client performance parameters Parameter Async queue size Buffer size for temporary tables Directory size Schema field cache size Hardlimit Local buffer size Maximum memory Record buffer size No Auto Result-list
PROLIB

(1 of 2) Purpose

Specify the total number of bytes allowed for asynchronous request buffers allocated for a client. Specify the size of the buffer pool for blocks or records from the temporary table. Change the number (soft limit) of compiled procedure directory entries. Change the number (soft limit) of entries in the schema field cache. Force OpenEdge to adhere to set limits. Specify the size (soft limit) of the local record buffer. Set the initial amount (soft limit) of memory allocated for r-code segments. Specify the standard record buffer size in bytes. Avoids building result-lists for static non-scrolling queries. Allocate a 512-byte cache for the OpenEdge library directory. Store r-code files locally in temporary sort files. Specify the stack size. Specify the number of 1KB blocks to allocate in the stash area. Specify the directory for temporary files.

-Bt n

-D n

-fc num-entries

-hardlimit -l n

-mmax n

-Mr n

-noautoreslist

-plm

memory swap

-pls -s n -stsh n

PROLIB

Stack size Stash area Temporary directory

-T dirname

33

Client product-type parameters Table 32: Syntax

-t

Client performance parameters Parameter Save temp files (UNIX only) Speed sort Purpose Make temporary file entries visible.

(2 of 2)

-TB blocksize

Specify the block size in kilobytes to allocate when sorting records for reports or rebuilding indexes. Specify the number of blocks or streams simultaneously merged during a sort.

-TM n

Merge number

Client product-type parameters

Use the parameters listed in Table 33 to control the nature of a client session. Table 33: Syntax
-rg

Client product-type parameters Parameter Run 4GL client Run query client Run run-time client Encrypted compiler mode Purpose Limit access or functionality of the session to the 4GL client. Limit access or functionality of the session to the Query client. Limit access or functionality of the session to the run-time client. Enable a query or run-time OpenEdge version to compile encrypted source code and access the Data Dictionary to manage schema (for example: for security management and to dump or load the .df file).

-rq

-rr

-rx

34

Progress 4GL parameters

Progress 4GL parameters

Use the parameters listed in Table 34 to modify Progress 4GL behavior. Table 34: Syntax
-b -baseADE

Client 4GL parameters Parameter Batch ADE r-code location Check Width Purpose

(1 of 4)

Initiate a batch process with no terminal interaction. Specify the ADE r-code directory to the client so the client can add this directory and all procedure libraries contained in the directory to the PROPATH. Specifies whether Progress compares CHARACTER, DECIMAL, and RAW field data against the metaschema _width field value before updating a database record. Allows an application to automatically write all error and warning messages to the specified log file. Change the number (soft limit) of compiled procedure directory entries. Start a session by running the Debugger in stand-alone mode. Access 4GL stack trace information during a session. Enables a Progress process (that is, a Progress 4GL client or a single WebSpeed agent) to attach to the attachable Debugger. Direct Progress to use dictionary and help validation for all fields in all frames when compiling. Sets the EXPANDABLE and FIT-LAST-COLUMN option to on for all browsers created in the current session. Control the conditions under which you want asynchronous COM events handled.

-checkwidth n

-clientlog

Client logging Directory size Debugger Debug alert

-D n

-debug

-debugalert

-debugReady {0|port-number}

Enable Attachable Debugging Dictionary expressions Expand browse Filtering asynchronous COM events

-dictexps

-expandbrow

-filterocxevents

35

Progress 4GL parameters Table 34: Syntax

-fldisable

Client 4GL parameters Parameter Field list disable Number of databases. Dynamics parameter Input characters Keyword forget list Lock timeout Log Entry Types Logging Level Log Threshold Number of Log Files to Keep Nested blocks No lock No Auto Result-list No Check temp-table names Purpose

(2 of 4)

Direct Progress to ignore field lists in the r-code and fetch complete records. Specify the maximum number of databases that can be connected. Specify a character string that can be accessed from 4GL procedures within the Dynamics framework. Expand the available buffer space for a single statement. Disable the keywords listed in filename. Specify a different lock wait timeout. Specifies one or more types of log entries to write to the log file. Specifies the level at which log entries are written to the log file. Specifies the file size threshold of log files. Specifies the number of rolled over log files to keep on disk at any one time. Set the maximum number (soft limit) of nested procedure blocks. Make all record retrieval statements default to NO-LOCK record access. Avoids building result-lists for static non-scrolling queries. Suppress the limited checking of temp-table column names when passing temp-tables as parameters to procedures.

-h n

-icfparam

-inp n

-k filename

-lkwtmo seconds -logentrytypes string -logginglevel n

-logthreshold n

-numlogfiles n

-nb n

-NL

-noautoreslist

-nochkttnames

36

Progress 4GL parameters Table 34: Syntax

-o printername

Client 4GL parameters Parameter Printer Outer-join mode Startup procedure Parameter Purpose

(3 of 4)

Identify the printer to use when processing OUTPUT TO PRINTER statements. Specify the mode in which mixed inner and left outer joins, in queries of three or more joined tables, are processed. Specify a procedure that executes when OpenEdge starts. Supply information in a character string or comma-separated list of files to open in Procedure Editor buffers. Specify the name of the host or the IP address of the host at which the HTTP-based proxy server is located. Authenticate the AppServer client to the HTTP-based proxy server. Specify the port on which the HTTP-based proxy server is listening. Authenticate an AppServer client to the HTTP-based proxy server. Direct OpenEdge to search PROPATH directories only on the first use of a procedure. Specify a different random number generator. Use the value 1 for the old generator or the value 2 for a new one. Direct OpenEdge to re-read the record from the database, even if the record is already in a buffer. Specify the maximum number of tokens allowed in a 4GL statement.

-ojmode

-p filename

-param string

-proxyhost

Proxy host

-proxyPassword

Proxy password Proxy port Proxy userid Quick request Alternate random number generator Reread nolock Token

-proxyport

-proxyUserid

-q

-rand n

-rereadnolock

-tok n

37

Client internationalization parameters Table 34: Syntax

-v6colon

Client 4GL parameters Parameter Version 6 colon Version 6 query Purpose Direct OpenEdge to use colon alignment of unlabeled fields (as in Version 6).

(4 of 4)

-v6q

Direct the OpenEdge server to use only a single index to resolve FOR EACH statements (as in Version 6).

Client internationalization parameters

Use the parameters listed in Table 35 to control the format in which data appears. Table 35: Syntax
-checkdbe

Client internationalization parameters Parameter Check double-byte enabled Conversion map Case table Collation table Internal code page Log file code page Print code page R-code in code page Purpose

(1 of 2)

Display compile-time warnings on 4GL statements and functions that may impact the handling of double-byte or extended-character data. Identify the conversion map file. Identify the case table that establishes case rules for the code page. Identify a collation table to use with the code page. Identify the code page that OpenEdge uses in memory. Identify the code page used for writing messages to the log file. Identify the code page used for printer output. Identify the code page used for reading r-code text segments.

-convmap filename -cpcase tablename

-cpcoll tablename
-cpinternal codepage -cplog codepage

-cpprint codepage -cprcodein codepage

38

Client internationalization parameters Table 35: Syntax

-cprcodeout codepage -cpstream codepage -cpterm codepage

Client internationalization parameters Parameter R-code out code page Stream code page Terminal code page Date format European numeric format Initial value segment no convert Language Fractional separator Thousands separator Four digit year default Century year offset Purpose

(2 of 2)

Identify the code page used for writing r-code text segments. Identify the code page used for stream I/O. Identify the code page for character terminals. Specify the format for displaying dates, using the three-character string of d, m, y in any order. Display in European numeric format. Disable a code page conversion that was not provided in earlier releases of OpenEdge. Identify the language with a character string, in quotes. Change the character that represents a numbers decimal point in formatted text. Change the character that represents a numbers thousands separator in formatted text. Output a four-digit year from EXPORT, MESSAGE and PUT UNFORMATTED statements that may use a two-digit year. Specify the start of the 100-year period used to define the two-digit DATE value.

-d dateform

-E

-isnoconv

-lng languagename -numdec numeric-value -numsep numeric-value -yr4def

-yy n

39

Session statistics parameters

Session statistics parameters

Use the parameters listed in Table 36 to collect statistics about client session activity and performance. Table 36: Syntax
-y -yc

Session statistics parameters Parameter Statistics Statistics with

CTRL-C

Purpose Collect procedure access and usage statistics. Substitute CTRL-C for executing the SHOW-STATS statement. Write segment statistics to the client monitor file (client.mon by default). Collect procedure call statistics and write them to an output file (proc.mon by default).

-yd

Segment statistics Statistics with cross-reference

-yx

310

Windows session parameters

Windows session parameters

Use the parameters listed in Table 37 to control a Windows session. Table 37: Syntax
-basekey name

Windows session parameters Parameter Registry base key1 Event level Initialization file1 Windows passthrough printing1 Windows single session Windows exitno dialog Purpose Identify the registry basekey to use for environment information. Specify the level of information written to the Windows Event Log. Identify the initialization registry sub-key or the applications initialization (.INI) file. Enable Windows Passthrough Printing mode.

-evtlevel value

-ininame name

-Wa -wpp

-wss

Limit a Windows GUI user to running one client session at a time. Prevent prompt for confirmation when Windows shuts down while OpenEdge is active.

-wy

You can use this parameter only on the command line. It is not supported in a parameter (.pf) file.

311

Client Connection parameters (CC)

Client Connection parameters (CC)

Use the Client Connection parameters when connecting to an OpenEdge Database Server, AdminServer, AppServer, or a non-OpenEdge DataServer. The parameters are organized alphabetically by syntax. For more information on connecting to a database, see OpenEdge Deployment: Managing 4GL Applications.

Client database connection parameters

Use the parameters listed in Table 38 to control how you connect to a specified database. If you use the Physical Database Name (-db) parameter to specify more than one database when you start a session, specify the connection parameters for each database after the database name to which they apply and before the next -db parameter, as shown. OpenEdge applies database connection parameters only to the previously specified database:

mpro

-db] db1-name

db1-parameters

-db db2-name

db2-parameters

Note: OpenEdge implicitly specifies the -db parameter for the first database. You can specify all other parameters anywhere on the command line. If you specify the same parameter more than once, OpenEdge uses the value you provide for the last instance of the parameter. Table 38: Syntax
-1 -B n

Client database connection parameters Parameter Single-user mode1 Blocks in database buffers1 Private read-only buffers Bleeding record lock Purpose

(1 of 3)

Start OpenEdge in single-user mode. Specify the number of database buffer blocks. Request a number of private read-only buffers. Hold a share lock on a released record used by more than one buffer.

-Bp n

-brl

312

Client database connection parameters Table 38: Syntax

-cache filename

Client database connection parameters Parameter Schema cache file Purpose

(2 of 3)

Read the database schema from a local file instead of the database. Override preset connection parameters for auto-connect databases. Change the maximum number of index levels. Identify one or more databases to connect to at startup. Connect through a NameServer to an ODBC or ORACLE DataServer. Open all files in unbuffered mode. Identify the database type. Allow access to a damaged database. Call Technical Support before using -F. Identify a remote host. Specify the number of hash table entries for the buffer pool. Run OpenEdge without database integrity or recovery. Stop a client from comparing time stamps when connection to an AS/400 database. Assign the logical database name. Delay writing the last before-image (BI) file records. Specify the message buffer size for network client/server protocols.

-cp

com-parms

filename -cs n

Communications parameter file Cursor size Physical database name DataService Direct I/O1, 2 Database type Force access Host name Hast table entries1 No crash protection1 AS/400 ignore stamp Logical database name Delayed BI file write1, 2 Message buffer size.

-db physical-dbname

-DataService data-service -directio -dt db-type -F

TCP: -H host-name SNA: PLU= plu-name -hash n

-i

-is

-ld logical-dbname

-MF n

-Mm n

313

Client database connection parameters Table 38: Syntax

-nohostverify

Client database connection parameters Parameter No Host Verify No Session Reuse Password3 Fast schema change Non-reliable I/O1 Read-only media Purpose

(3 of 3)

Turns off host verification for a Secure Sockets Layer (SSL) connection. Avoids the reuse of a Secure Sockets Layer (SSL) session ID. Specify a user password. Turn off Fast schema change. Enable buffered I/O to the before-image file. Open a database for read-only access. Identify the service and port number to use on the host machine when connecting to a broker process. Specify that the Server program on an AS/400 start with an OpenEdge connection request (SNA only). Specifies a Secure Socket Layer connection. Identify the directory or library containing the 4GL triggers for a database. Specify the user ID.

-nosessionreuse

-P password -populate -r

-RO -S

servicename

Service name

port-number -Sn

}
AS/400 server program name SSL-based connection

-ssl

-trig

dir-name

Trigger location

lib-name

}
User ID3

-U userid
1 2 3

Single-user database connections only; otherwise, use only for server startup. UNIX, Windows only. Different meaning for non-OpenEdge databases.

314

OpenEdge Database Server parameters (DBS)

OpenEdge Database Server parameters (DBS)

The OpenEdge Database Server parameters are organized alphabetically by syntax in the following subcategories: Database server performance parameters Database server-type parameters Database server internationalization parameters Database server statistics collection parameters Database server network parameters

Database server performance parameters

Use the parameters listed in Table 39 to optimize server performance. Table 39: Syntax
-aibufs n

Server performance parameters Parameter After-image buffers After-image stall Blocks in database buffers Maximum private buffers per connection Before-image buffers Threshold stall Purpose

(1 of 3)

Specify the number of after-image buffers when running AIW. Suspend database activity when an empty after-image (AI) file is unavailable. Specify the number of blocks in the database buffers. Control the number of private buffers a connection can request through the Private Read-only Buffers (-Bp) parameter. Specify the number of before-image buffers when running BIW. Send a message to the log file when the recovery log threshold is reached. Use with -bithold.

-aistall

-B n

-Bpmax

-bibufs n

-bistall

315

Database server performance parameters Table 39: Syntax

-bithold n

Server performance parameters Parameter Recovery log threshold Direct I/O (UNIX, Windows only) Before-image cluster age Group delay Hash table entries No crash protection Lock table entries Purpose

(2 of 3)

Specify the maximum size of the recovery log files. Open all files in unbuffered mode.

-directio

-G n

Specify the number of seconds before OpenEdge reuses a before-image cluster. Specifies the number of milliseconds a transaction waits before committing. Specify the number of hash table entries for the buffer pool. Run OpenEdge without using database integrity or recovery. Specify the number of entries in the record locking table. Delay writing the last before-image (BI) file records. Specify the message buffer size for network client/server protocols. Allocate shared memory in multiples of 8MB for VLM64 support. Replace the default value of the shared-memory overflow area.

-groupdelay n

-hash

-i

-L n

-Mf

Delayed BI file write (UNIX, Windows only) Message buffer size VLM page table entry optimization (digital UNIX only) Shared-memory overflow size (UNIX, Windows only) Number of users Pending Connection Time

-Mm n

-Mpte

-Mxs n

-n n

Specify the maximum number of users connected to the database. Specify the amount of time a client has to connect to a server before the broker clears the clients reservation.

-PendConnTime n

316

Database server performance parameters Table 39: Syntax

-pinshm

Server performance parameters Parameter Pin shared memory Semaphore sets (UNIX only) Spin lock retries (UNIX, Windows only) SQL Open Cursors SQL stack size SQL statement cache size SQL Sorting Memory SQL Sorting on Disk SQL Temp Table Data Page Purpose

(3 of 3)

Prevent the database engine from swapping shared memory contents to disk. Change the number of semaphore sets available to a broker. Specify the number of times a process tries to acquire a latch before pausing. Specify the maximum number of cursors open at any one time. Specify the size, in MB, of the SQL Stack. Specify the number of statements allowed in the SQL statement cache. Defines the size of the temporary table buffer in memory. Defines the size of the temporary table for backup storage. Defines the size of the temporary table data page.

-semsets n

-spin n

-SQLCursors value -SQLStack n -SQLStmtCache num_entries -SQLTempBuff value -SQLTempDisk value -SQLTempPgSize value

317

Database server-type parameters

Database server-type parameters

Use the parameters listed in Table 310 to start a particular type of server. Table 310: Syntax
-m1

Server-type parameters Parameter Auto server Manual server (UNIX, Windows only) Secondary login broker (UNIX, Windows only) Type of server to start Purpose Start an auto server. Used internally by the database broker. Manually start a remote user server after you start a broker. Start a secondary broker. Specify whether to start a 4GL server, SQL server, or both.

-m2

-m3

-ServerType

[4GL|SQL|Both]

Database server internationalization parameters

Use the parameters listed in Table 311 to control the format in which data appears. Table 311: Server internationalization parameters Parameter Conversion map Case table Collation table Internal code page Log file code page Purpose Identify the conversion map file. Identify the case table that establishes case rules for the code page. Identify a collation table to use with the code page. Identify the code page that OpenEdge uses in memory. Identify the code page used for writing messages to the log file. (1 of 2)

Syntax
-convmap filename -cpcase tablename

-cpcoll tablename

-cpinternal code-page

-cplog code-page

318

Database server statistics collection parameters Table 311: Server internationalization parameters Parameter Print code page R-code in code page Stream code page Terminal code page Purpose Identify the code page used for printer output. Identify the code page used for reading r-code text segments. Identify the code page used for stream I/O. Identify the code page for character terminals. (2 of 2)

Syntax
-cpprint code-page

-cprcodein code-page

-cpstream code-page

-cpterm code-page

Database server statistics collection parameters

Use the parameters listed in Table 312 to collect statistics for table and index access. Table 312: Syntax
-baseindex n

Server statistics collection parameters Parameter Base index Purpose Specify a range of indexes for which you want to collect statistics. Use with -indexrangesize. Specify a starting table number in a range of tables for which you want to track access statistics. Use with -tablerangesize. Specify the number of indexes to track for access statistics. Specify the number of tables for which you want to collect statistics.

-basetable n

Base table

-indexrangesize n

Index range size Table range size

-tablerangesize n

319

Database server network parameters

Database server network parameters

Use the parameters listed in Table 313 to supply OpenEdge with necessary network information. Table 313: Server network parameters Parameter AdminServer port SQL server Java classpath Host name Key Alias Purpose Connect a servergroup and an AdminServer. Identify the Java classpath to use when starting an SQL server. Specify a remote host. Specify the alias name of a Secure Sockets Layer (SSL) private key/digital certificate key-store. Specify the encrypted Secure Sockets Layer (SSL) key alias password. Specify the maximum number of remote users per database server. Specify the highest accessible port number in a specified range. Specify the number of remote users on a server before a broker starts another server. Specify the lowest accessible port number in a specified range. Specify the maximum number of remote client servers that a broker can start. Specify the maximum number of servers to serve remote users for a protocol. (1 of 2)

Syntax
-adminport

{ service-name| port }
-classpath pathname

TCP: -H host-name SNA: -H PLU= plu-name -keyalias key-alias-name

-keyaliaspasswd key-alias-password -Ma n

Key Alias Password Maximum clients per server1 Maximum dynamic server1 Minimum clients per server1 Minimum dynamic server1 Maximum servers1 Servers per protocol1

-maxport n

-Mi n

-minport n

-Mn n

-Mp n

320

Database server network parameters Table 313: Server network parameters Parameter Maximum servers per broker1 No Session Cache Configuration properties file Service name Purpose Specify the maximum number of servers that multiple brokers can start to serve remote users for a protocol. Disables the SEcure Sockets Layer (SSL) session caching. Identify the properties file an AdminServer uses when starting a database server or servergroup. Specify the service or port number to be used by a broker process. Identify a logical collection of server processes to start. Specify the length of time a SSL session is held in SSL session cache. Specifies a Secure Socket Layer (SSL) to all database and client connections. (2 of 2)

Syntax
-Mpb n

-nosessioncache

-properties filename

-S

service-name

port-number

}
Server group Session Timeout SSL-based Connection

-servergroup name

-sessiontimeout n

-ssl

UNIX, Windows only.

321

DataServer parameters (DS)

DataServer parameters (DS)

Use the parameters listed in Table 314 when starting an ODBC, ORACLE, or MS SQL Server DataServer. The parameters are organized alphabetically by syntax. Table 314: DataServer parameters Syntax
-c n

(1 of 2) Purpose Specify the number of index place holders or cursors. Identify the code page that OpenEdge uses in memory. Identify the code page used for writing messages to the log file. Identify the code page used for printer output. Identify the code page used for reading r-code text segments. Identify the code page used for stream I/O. Identify the code page for character terminals. Identify keywords as parameters for the ODBC, ORACLE, or MS SQL Server DataServer. Identify the database type. Specify a remote host. Stop a client from comparing time stamps when connecting to an AS/400 database. Stop an ORACLE DataServer from providing index hints to the ORACLE DBMS.

Parameter Index cursors Internal code page Log file code page Print code page R-code in code page Stream code page Terminal code page

-cpinternal code-page

-cplog

code-page

-cpprint code-page

-cprcodein code-page

-cpstream code-page

-cpterm code-page

-Dsrv keyword ( , value ) , keyword2 ( , value2 ) -dt db-type

[ DataServer ... ]
Database type Host name AS/400 ignore stamp Index hint

TCP: -H host-name SNA: -H PLU= plu-name

-is

-noindexhint

322

Startup Parameter Usage Categories Table 314: DataServer parameters Syntax

-nojoinbysqldb

(2 of 2) Purpose Make a client evaluate and perform queries that have joins. Turn off SELECT pass Through for OBDC and ORACLE DataServers. Start a Server program on an AS/400 with a OpenEdge connection request (SNA only).

Parameter Server join SELECT pass through disable AS/400 server program name

-noSQLbyserver

-Sn

323

OpenEdge Deployment: Startup Command and Parameter Reference

324

4
Startup Parameter Descriptions
This chapter describes the OpenEdge startup parameters in detail, in alphabetical order by syntax. Each section begins with a table showing the syntax of the parameter and other information about it. The Use with table column indicates the usage categories of the parameter. The usage categories are: Client Connection (CC), to use when connecting to a specific database. Client Session (CS), to use when starting any client session. Database Server (DBS), to use when starting a server or broker. DataServer (DS), to use when starting non-OpenEdge DataServers. Open Interface Driver (OID), to use when starting the Open Interface Driver.

For a quick reference to the parameters, see Chapter 3, Startup Parameter Usage Categories.

Single-user Mode (-1)

Single-user Mode (-1)

Operating system and syntax Use with CC UNIX Windows Maximum value Minimum value

-1

Single-user default

Multi-user default

Use Single-user Mode (-1) with an OpenEdge executable module to start OpenEdge in single-user mode. In this mode, only one user can access the database. The PRO command invokes the OpenEdge executable with -1 by default, but only for the first database named on the command line. Each additional database must already have a server running in multi-user mode, unless -1 is added to its parameter list. In the following example, db1 and db3 are connected in single-user mode; db2 is connected in multi-user mode:

pro db1 -db db2 -db db3 -1

42

AdminServer Group (-admingroup)

AdminServer Group (-admingroup)

Operating system and syntax Use with CC
user-group

UNIX Windows Maximum value

-admingroup user-group[:user-group]

Minimum value

Single-user default

Multi-user default

The name of the group of users. There must be a minimum of one valid group or the AdminServer will not start. If multiple groups are listed, they are separated by a colon. The user starting the AdminServer must be a valid account in one of the groups. Use AdminServer Group (-admingroup) to authorize OpenEdge AdminServer access and operational privileges for one or more user groups. To perform AdminServer functions, a user must use a valid user account that appears in at least one of the user groups. On UNIX, you can specify a user group as any local group name or NIS group name. Subgroups are not supported. On Windows, you can specify a user group as any local group name or Domain group name. Global groups as members of local groups are supported. If, during the OpenEdge installation process, you accepted the default installation and did not choose to use authorization, you can use this parameter when starting the AdminServer to select authorization for one or more user groups. Otherwise, no group authorization is defined and all users have authorization.

43

AdminServer Port (-adminport)

AdminServer Port (-adminport)

Operating system and syntax Use with DBS
service-name

UNIX Windows Maximum value

-adminport service-name port

Minimum value

Single-user default

Multi-user default

The name of the service to be used by the AdminServer.

port

The port number the AdminServer uses to communicate with servergroups. Use AdminServer Port (-adminport) to establish communication between a servergroup and an AdminServer. The AdminServer uses this parameter internally. The default is none, and the server does not attempt to connect to an AdminServer. You do not usually use this parameter directly. The -adminport setting must match the -admin setting specified when the AdminServer was started.

44

After-image Buffers (-aibufs)

After-image Buffers (-aibufs)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value Minimum value 1

-aibufs n

Single-user default

Multi-user default 5

The number of after-image buffers to use. Use After-image Buffers (-aibufs) to specify the number of after-image buffers. This parameter is useful only when running the after-image writer (AIW) because the AIW writes the filled After-image Buffers to disk, making the buffers available to other client and server processes. Progress Software recommends you set -aibufs to a value of 1.5 times the value of the Before-image Buffers (-bibufs) parameter, or a minimum of 5. Without the AIW writing the buffers, any gain from increasing the number of buffers is negligible.

45

After-image Stall (-aistall)

After-image Stall (-aistall)

Operating system and syntax Use with DBS UNIX Windows Maximum value Minimum value

-aistall

Single-user default

Multi-user default

Use After-image Stall (-aistall) to suspend database activity if all AI files are filled. Then wait until the next AI file is backed up and marked empty and send this message to the database log file:

Cant switch to after-image extent filename it is full. (3775) Backup ai extent and mark it as empty (3776)

This way you can empty an AI file instead of shutting down the database. When using after-image (AI) files, you monitor the status of the files to ensure that you do not attempt to reuse an unavailable file. If all the AI files are filled and Progress cannot switch to an empty one, by default the database shuts down. See OpenEdge Data Management: Database Administration for information on using the after imaging feature.

46

Async Queue Size (-asyncqueuesize)

Async Queue Size (-asyncqueuesize)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value 2,147,483,647 Minimum value 1

-asyncqueuesize n

Single-user default

Multi-user default

The total number of bytes allowed for all asynchronous request buffers allocated for a client. Use Async Queue Size (-asyncqueuesize) to specify the total number of bytes allowed for all buffers allocated when asynchronous requests are queued on behalf of a client. This number determines how many buffers to allocate for each client connection. Each buffer is at most 8KB. If you do not specify -asyncqueuesize, the default size for all buffers is 64KB. As each client connects, request buffers are generated and the size of each buffer determined. Both send and receive requests can be queued on a client depending how the program is implemented. When the buffers are filled, additional queued requests are stored in a temporary table associated with that client session. If you set the value of -asyncqueuesize to 0, all requests are placed in the temporary table. Performance may vary based upon whether requests are stored in memory or in the temporary table. So you may want to choose this value based upon how much data you expect to flow between the client and the AppServer for asynchronous requests. Note: You can use -asyncqueuesize only when a client making asynchronous requests is connecting to an AppServer. The client may be an AppServer. The following example shows how to start a multi-user mode OpenEdge client session using -asyncqueuesize:

mpro -asyncqueuesize 135000

47

Blocks in Database Buffers (-B)

Blocks in Database Buffers (-B)

Operating system and syntax Use with CC, DBS UNIX Windows Maximum value1 System dependent1 Minimum value 10

-B n

Single-user default 20

Multi-user default (8 * users) 2

1 2

Limited by available memory. The users value is specified by the Number of Users (-n) parameter.

The number of blocks in the database buffers. Use database buffers (-B) to specify the number of blocks in the database buffers. The optimum value depends on your application. See OpenEdge Data Management: Database Administration for more information.

48

Batch (-b)

Batch (-b)
Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-b

Single-user default

Multi-user default

Use Batch (-b) to initiate a batch session, with no terminal interaction. When procedures run in batch mode, Progress does not display any messages produced by those procedures on the terminal screen.

49

ADE R-code Location (-baseADE)

ADE R-code Location (-baseADE)

.

Operating system and syntax Use with CS

<directory>

UNIX Windows Maximum value Minimum value

-baseADE directory

Single-user default

Multi-user default

Identifies where the client should look for the ADE r-code. You can have different versions of ADE r-code on the same machine at the same time. As a result, you need a way to specify the ADE r-code directory to the client so that the client can add this directory and all of the procedure libraries contained in the directory to the PROPATH. The -baseADE startup parameter lets you specify the location of the ADE r-code directory. At session startup, OpenEdge automatically adds $DLC/gui (or $DLC/tty for character mode clients) and all procedure libraries in $DLC/gui (or $DLC/tty) to PROPATH. When you specify -baseADE, the $DLC/gui (or $DLC/tty) directory and the procedure libraries in $DLC/gui (or $DLC/tty) are not added to PROPATH. Instead, the directory specified using the -baseADE startup parameter is added to PROPATH followed by all of the procedure libraries in the directory. For example, if you use -baseADE to specify the following:
-baseADE c:\maint\gui

And c:\maint\gui contains the following procedure libraries: adecomm.pl, adeuib.pl, and protools.pl. The PROPATH looks like the following:
...,c:\maint\gui,c:\maint\gui\adecomm.pl,c:\maint\ gui\adeuib.pl,c:\maint\gui\protools.pl,...

If $DLC/gui (or $DLC/tty) or any of the procedure libraries from the directory already are part of PROPATH (environment variable, .ini file, or registry setting), OpenEdge does not remove them.

410

ADE R-code Location (-baseADE) OpenEdge allows you to specify an empty string for <directory>, -baseADE "". In this situation, OpenEdge does not add $DLC/gui (or $DLC/tty) or the procedure libraries in $DLC/gui (or $DLC/tty) to PROPATH. You also can specify the ADE R-code Location with the BASE-ADE attribute of the SESSION system handle. For more information about this SESSION attribute, see the OpenEdge Development: Progress 4GL Reference.

411

Base Index (-baseindex)

Base Index (-baseindex)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value Minimum value

-baseindex n

Single-user default

Multi-user default

The starting index number in the range of indexes for which you want to track access statistics. Use Base Index (-baseindex) with Index Range Size (-indexrangesize) to specify the range of indexes for which you want to collect statistics. Access to the statistics is handled through the Virtual System Tables (VSTs). Index statistics are stored in the _IndexStat VST. See OpenEdge Data Management: Database Administration for more information on virtual system tables. To obtain index numbers, use the following 4GL code:

FOR EACH _file: DISPLAY _file.file-filename. FOR EACH _index WHERE index.file-recid = RECID(file): DISPLAY _idx-num _index-name. END. END.

This results in the following output:

File-Name filename _idx-num Index-Name n1 index name1 n2 index name2 n3 index name3

412

Registry Base Key (-basekey)

Registry Base Key (-basekey)

Operating system and syntax Use with CS
name

Windows Maximum value Minimum value

-basekey name

Single-user default

Multi-user default

The name of the registry basekey. Use Registry Base Key (-basekey) to identify the registry basekey in which to look for environment information. You can force OpenEdge to bypass the registry search by specifying INI. Valid values are:
HKEY_CURRENT_USER HKEY_CLASSES_ROOT HKEY_LOCAL_MACHINE HKEY_USERS HKEY_CURRENT_CONFIG HKEY_DYN_DATA INI

Note: You can use the -basekey startup parameter only at the command line. It is ignored when used in a parameter (.pf) file. See OpenEdge Deployment: Managing 4GL Applications for more information on using the -basekey startup parameter.

413

Base Table (-basetable)

Base Table (-basetable)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value Minimum value

-basetable n

Single-user default

Multi-user default

The starting table number in the range of tables for which you want to track access statistics. Use Base Table (-basetable) with Table Range Size (-tablerangesize) to specify the range of tables for which you want to collect statistics. Access to the statistics is handled through the Virtual System Tables (VSTs). Table statistics are stored in the _TableStat VST. See OpenEdge Data Management: Database Administration for more information on virtual system tables. To obtain table numbers, use the following 4GL code:

FOR EACH _file: DISPLAY _file-num _file-filename. END.

This results in the following output:

_File-Number File-Name n1 table name1 n2 table name2 n3 table name3

414

Before-image Buffers (-bibufs)

Before-image Buffers (-bibufs)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value Minimum value 3

-bibufs n

Single-user default

Multi-user default 5

The number of before-image buffers. Use Before-image Buffers (-bibufs) to specify the number of before-image buffers. This parameter is useful only when running the before-image writer (BIW). The BIW continually writes the filled before-image buffers to disk, making the buffers available to other client and server processes. Without a BIW writing the buffers, any gain from increasing the number of buffers is negligible. See OpenEdge Data Management: Database Administration for more information on setting this parameter.

415

Threshold Stall (-bistall)

Threshold Stall (-bistall)

Operating system and syntax Use with DBS UNIX Windows Maximum value Minimum value

-bistall

Single-user default

Multi-user default

Use Threshold Stall (-bistall) with Recovery Log Threshold (-bithold) to quiet the database when the recovery log threshold is reached, without performing an emergency shutdown. When you use -bistall, a message is added to the database log (.lg) file stating that the threshold stall is enabled.

416

Recovery Log Threshold (-bithold)

Recovery Log Threshold (-bithold)

Operating system and syntax Use with DBS UNIX Windows Maximum value System dependent1 Minimum value System dependent1

-bithold n

Single-user default

Multi-user default

Limited by available disk space.

An integer specifying the threshold, in MB. Use Recovery Log Threshold (-bithold) to set the maximum size to which recovery log files can grow. The recommended threshold is between 3% and 100% of the largest possible recovery log file size, rounded to the nearest cluster boundary. If the threshold is set above 1000MB, OpenEdge issues a warning message to the display and the database log (.lg) file. Once the threshold is reached, the database performs an emergency shutdown. See OpenEdge Data Management: Database Administration for more information about recovery logs.

417

Private Read-only Buffers (-Bp)

Private Read-only Buffers (-Bp)

Operating system and syntax Use with CC
n

UNIX Windows Maximum value 64 Minimum value 1

-Bp n

Single-user default

Multi-user default

An integer value greater than 1 but less than 64. Use Private Read-only Buffers (-Bp) to request a number of private read-only buffers. The request remains active for the entire session unless it is changed or disabled by an application. Each user of private read-only buffers reduces the number of public buffers, which is set with Blocks in Database Buffers (-B). Note: The total number of private read-only buffers for all simultaneous users is limited to 25% of the total blocks in database buffers.

418

Maximum Private Buffers per Connection (-Bpmax)

Maximum Private Buffers per Connection (-Bpmax)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value 25% of -B Minimum value 1

-Bpmax n

Single-user default 64

Multi-user default 64

An integer specifying the maximum number of private buffers. The Maximum Private Buffers per Connection (-Bpmax) parameter is a broker setting which controls the number of private buffers a connection can request through the private read-only buffers (-Bp) parameter. The number of blocks in the database buffers is controlled by the blocks in database buffers (-B) parameter. Up to 25% of the blocks created may be allocated for use as private buffers. When a client connects to an OpenEdge database, the connection requests -Bp n private buffers. Prior to 9.1C, the maximum value of -Bp was 64. With the -Bpmax parameter, the broker may override this limit by allowing the value of -Bp to be up to 25% of -B. Note: Each use of a private read-only buffer reduces the number of public buffers. The total number of private buffers for all simultaneous users is limited to 25% of the total blocks in database buffers.

419

Bleeding Record Lock (-brl)

Bleeding Record Lock (-brl)

Operating system and syntax Use with CC UNIX Windows Maximum value Minimum value

-brl

Single-user default

Multi-user default

Use Bleeding Record Lock (-brl) to let Progress hold a share lock on a record used by more than one buffer, even after the buffer using the record releases it.

420

Buffer Size for Temporary Tables (-Bt)

Buffer Size for Temporary Tables (-Bt)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value 50,000 Minimum value 10

-Bt n

Single-user default

Multi-user default

An integer that specifies the number of blocks in the buffer for temporary tables. Use Buffer Size for Temporary Tables (-Bt) to specify the size of the buffer pool for blocks/records from the temporary table. OpenEdge uses the value you specify for temporary databases used during the session the same way it uses Blocks in Database Buffers (-B) for permanent databases. The default value is 10. See OpenEdge Development: Progress 4GL Handbook for more information on temporary tables.

421

Index Cursors (-c)

Index Cursors (-c)

Operating system and syntax Use with DS
n

UNIX Windows Maximum value Minimum value

-c n

Single-user default

Multi-user default

The number of index cursors allowed. Use Index Cursors (-c) to specify the number of index place holders, or cursors, for an OpenEdge session. Each active FOR EACH and FIND NEXT loop uses one index cursor for each index OpenEdge is using. A cursor takes 64 bytes. If you need more index cursors, OpenEdge displays the following error message:

SYSTEM ERROR: Too few index cursors. Increase -c parameter.

Note: The -c parameter has a different meaning when you connect to an ORACLE database. For more information, see OpenEdge Data Management: DataServer for ORACLE.

422

Schema Cache File (-cache)

Schema Cache File (-cache)

Operating system and syntax Use with CC
filename

UNIX Windows Maximum value Minimum value

-cache filename

Single-user default

Multi-user default

The pathname of a binary schema cache file. Use Schema Cache File (-cache) to read the database schema from a local file instead of the database. You must have previously built the schema cache and stored it as a binary file. To perform database activities, the OpenEdge client keeps a copy of the database schema called the schema cache in memory. By default, OpenEdge creates the schema cache by reading the database schema stored in the database file. The time required to read the schema usually is minimal; however, under the following conditions, the time required to read the schema might be unacceptable: If the client connects to the database over a wide-area network (WAN). When a large number of clients connect to a database simultaneously. For example, after a database shutdown or crash.

Connection time depends on several factors, including schema size. To reduce connection time, OpenEdge lets you store the schema cache as a binary file, called a schema cache file, on a local disk. The client can then read the schema directly from the schema cache file. To write the schema cache file, you build the desired schema cache and save it to a binary file using the Progress SAVE CACHE statement. The schema cache file is portable across systems, so you can create the file once and distribute it across a heterogeneous network of systems. For information on building and saving the schema cache file, see OpenEdge Development: Progress 4GL Handbook.

423

Schema Cache File (-cache) If you specify schema cache file (-cache) when you connect to a database and the local schema is valid, Progress reads the schema from the local file instead of from the database. The schema cache is valid if the time stamp of the schema cache file matches the time stamp in the database master block. If the time stamps do not match, or for some reason Progress cannot read the file, Progress issues a warning message and reads the schema from the database. Note: If you are generating the local binary schema cache, do not connect to the database using Trigger Location (-trig) and Schema Cache File (-cache) together.

424

Check Double-byte Enabled (-checkdbe)

Check Double-byte Enabled (-checkdbe)

Operating system and syntax UNIX Windows Maximum value Minimum value

-checkdbe

with CS

Single-user default

Multi-user default

Use Check Double-byte Enabled (-checkdbe) when you modify an OpenEdge application to support double-byte characters or extended character data. The -checkdbe parameter specifies that Progress generates compile-time warning messages whenever it finds a LENGTH function, SUBSTRING function, SUBSTRING statement, or OVERLAY statement without a CHARACTER, COLUMN, RAW, or FIXED option.

425

Check Width (-checkwidth)

Check Width (-checkwidth)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value Minimum value

-checkwidth n

Single-user default

Multi-user default

The check-width mode. Use Check Width (-checkwidth) to specify whether Progress compares CHARACTER, DECIMAL, and RAW field data against the metaschema _width field value before updating a database record. The _width field value specifies the maximum width of the data allowed in a field. Progress allows for variable length data; SQL does not. This startup parameter lets you impose the SQL requirement that data cannot exceed the size specified in the _width field. The valid check-width modes are: 0 Ignore the _width field value and store the data. This is the default mode. 1 Store the data, and generate a warning message if the data exceeds the size specified in the _width field. 2 Do not store data that exceeds the size specified in the _width field, and generate an error. Specify this mode if you want Progress to behave like SQL.

Note: The _width field value for array fields is the size of all array elements after Progress converts the array element values to CHARACTER. This means that even with the -checkwidth startup parameter enabled, array fields can still surpass the _width field value.

426

SQL Server Java Classpath (-classpath)

SQL Server Java Classpath (-classpath)

Operating system and syntax Use with DBS
pathname

UNIX Windows Maximum value Minimum value

-classpath pathname

Single-user default

Multi-user default

Specifies the pathname of the classpath. Use SQL Classpath (-classpath) to identify the Java classpath to use when starting an SQL server. SQL database brokers use this parameter when launching the Java Virtual Machine (JVM) to execute stored procedures. The default is to use the current environment variable CLASSPATH setting. You do not use this parameter directly.

427

Client Logging (-clientlog)

Client Logging (-clientlog)

Operating system and syntax Use with CS
filename

UNIX Windows Maximum value Minimum value

-clientlog filename

Single-user default

Multi-user default

The name of log file OpenEdge uses for messages and 4GL stack trace information. If the filename you supply is a relative pathname, then a file is accessed relative to the current working directory. If the filename is an absolute pathname, then the specified file is accessed. Note: Do not include a numbered sequence in the filename. This might conflict with the rolled over log files OpenEdge creates based on your Number of Log Files to Keep (-numlogfiles) and Log Threshold (-logthreshold) startup parameter settings. Client Logging (-clientlog) allows an application to automatically write error and warning messages to the specified log file. Use the Log Entry Types (-logentrytypes) startup parameter to specify one or more types of log entries you want to write to the log file. Use the Logging Level (-logginglevel) startup parameter to specify the level at which log entries are written to the log file. When you use the -clientlog startup parameter, and you also specify the Debug Alert (-debugalert) startup parameter or set SESSION:DEBUG-ALERT to yes, the log includes a 4GL stack trace for each log entry. If an error message is diverted to the ERROR-STATUS system handle, and client logging is enabled, then no information is written to the log file. In a non-interactive session, the application is configured so that the output device is associated with a file (or another device). In this configuration, when a Progress statement encounters an error, it writes the error to the output device. If client logging is enabled, then this message is also written to the specified log file. Errors are written to the output device at logging level 1 (Error) and up.

428

Client Logging (-clientlog) You can use the MESSAGE statement with the VIEW-AS ALERT-BOX option to write application specific information to the screen and the log file. In this case, you must specify an entry type of 4GLMessages and a logging level of 2 (Basic), at least. For more information about logging levels, see the Logging Level (-logginglevel) startup parameter reference entry. For more information about specifying log entry types, see the Log Entry Types (-logentrytypes) startup parameter reference entry. You can also use attributes on the LOG-MANAGER system handle to specify log entry types and logging levels. For more information about the Progress 4GL language elements referenced above, see the OpenEdge Development: Progress 4GL Reference. When -debug-alert is on and an error occurs in a batch session for: A 4GL batch client, Progress records the 4GL stack trace information in the log file specified with -clientlog. In this case, Progress lists the stack trace information in reverse order. That is, the procedure that generated the error is written first, and the root procedure is written last. An AppServer client or a WebSpeed agent, Progress records the 4GL stack trace information in their respective log files, also in reverse order. If you view one of these log files in the Progress Explorer, it appears in top-down order since Explorer displays log files in reverse order.

The code page used for the log file is -cpinternal and no conversions are performed for these log files. For more detailed information about enabling logging, see OpenEdge Development: Debugging and Troubleshooting.

429

Conversion Map (-convmap)

Conversion Map (-convmap)

Operating system and syntax Use with CS, DBS
filename

UNIX Windows Maximum value Minimum value

-convmap filename

Single-user default

Multi-user default

Pathname of your CONVMAP file. Use Conversion Map (-convmap) to identify the CONVMAP file to use for code page conversions, collation orders, and case conversions. By default, Progress uses the convmap.cp file in the DLC directory. You can create a CONVMAP file by using the PROUTIL utility with the CODEPAGE-COMPILER qualifier. See OpenEdge Development: Internationalizing Applications for more information on CONVMAP files.

430

Communications Parameter File (-cp)

Communications Parameter File (-cp)

Operating system and syntax Use with CC
com-parms, filename

UNIX Windows Maximum value

-cp

{ com-parms | filename }
Single-user default Multi-user default

Minimum value

The database connection parameters or parameter file. Use Communications Parameter File (-cp) to override preset connection parameters for auto-connect databases. Communications parameters supplied with the -cp parameter override any connection information stored in the Progress metaschema field _Db-comm in the _Db file record for the database.

431

Case Table (-cpcase)

Case Table (-cpcase)

Operating system and syntax Use with CS, DBS, OID
tablename

UNIX Windows Maximum value Minimum value

-cpcase tablename

Single-user default Basic

Multi-user default Basic

Name of a case table in the convmap.cp file. Use Case Table (-cpcase) to specify the case table. This table establishes case rules for the code page that Progress uses in memory. The code page is specified by the Internal Code Page (-cpinternal) parameter. The case rules are used by the CAPS and LC functions. Also, in a character field format, you can use an exclamation point (!) to tell Progress to convert all characters to uppercase during input. To retrieve the value of this startup parameter at runtime, use the SESSION system handle.

432

Collation Table (-cpcoll)

Collation Table (-cpcoll)

Operating system and syntax Use with CS, DBS, OID
tablename

UNIX Windows Maximum value Minimum value

-cpcoll tablename

Single-user default Basic

Multi-user default Basic

The name of a collation table within the convmap.cp file, or the name of a collation in the International Components for Unicode (ICU) library. Use Collation Table (-cpcoll) to identify a collation table that Progress uses with the code page in memory. The code page is specified by the Internal Code Page (-cpinternal) parameter. Progress uses the collation rules that you specify to compare characters and sort records if a BY clause cannot be satisfied by an index. The collation rules specified with the -cpcoll parameter take precedence over the collation specified for any database Progress accesses during the session, except when Progress uses or modifies pre-existing indexes. When you update or rebuild a databases indexes, Progress uses the collation rules originally defined for that database. If you do not use -cpcoll, Progress uses the language collation rules defined for the first database on the command line. If you do not specify a database on the command line, Progress uses the collation rules with the name basic. To retrieve the value of this startup parameter at runtime, use the SESSION system handle. See OpenEdge Development: Internationalizing Applications for more information on collation tables.

433

Internal Code Page (-cpinternal)

Internal Code Page (-cpinternal)

Operating system and syntax Use with CS, DBS, DS, OID
code-page

UNIX Windows Maximum value Minimum value

-cpinternal code-page

Single-user default iso8859-1

Multi-user default iso8859-1

Name of the code page that Progress uses in memory. Use Internal Code Page (-cpinternal) to identify the code page that Progress uses in memory and for graphical clients. For graphical clients, the -cpinternal code page should be the same code page that the operating system uses. If you do not use -cpinternal, the iso8859-1 code page is used by default. Note: Do not use a 7-bit table with -cpinternal. Use 7-bit tables for converting data from a 7-bit terminal to another code page only. Do not use them for character conversion in memory or for the database. To retrieve the value of this startup parameter at runtime, use the CPINTERNAL attribute of the SESSION system handle.

434

Log File Code Page (-cplog)

Log File Code Page (-cplog)

Operating system and syntax Use with CS, DBS, DS, OID
code-page

UNIX Windows Maximum value Minimum value

-cplog code-page

Single-user default -cpstream

Multi-user default -cpstream

Name of the code page for messages written to the log file. Use Log File Code Page (-cplog) to identify the code page that Progress uses to write messages to the log (.lg) file. If you do not specify a value, the default is the code page specified by Stream Code Page (-cpstream). To retrieve value of this startup parameter at runtime, use the CPLOG attribute of the SESSION system handle.

435

Print Code Page (-cpprint)

Print Code Page (-cpprint)

Operating system and syntax Use with CS, DBS, DS. OID
code-page

UNIX Windows Maximum value Minimum value

-cpprint code-page

Single-user default -cpstream

Multi-user default -cpstream

Name of the code page used for printer output. Use Print Code Page (-cpprint) to identify the code page Progress uses when it prints. When you print a file, the code page specified by -cpprint overrides the code page specified by Stream Code Page (-cpstream). To retrieve the value of this startup parameter at runtime, use the SESSION system handle.

436

R-code in Code Page (-cprcodein)

R-code in Code Page (-cprcodein)

Operating system and syntax Use with CS, DBS, DS, OID
code-page

UNIX Windows Maximum value Minimum value

-cprcodein code-page

Single-user default -cpinternal

Multi-user default -cpinternal

Name of the code page for reading r-code text segments. Use R-code in Code Page (-cprcodein) to read the r-code text segments, as if they were written in the code page specified by -cprcodein, and convert them to the Internal Code Page (-cpinternal) code page. Usually when Progress reads r-code, it converts text segments to the code page specified by Internal Code Page (-cpinternal). Caution: This parameter is for use during very rare situations and in general should not be used. Progress reads text segments as if they are written in the code page specified by -cprcodein, even if the text segments were written with a different code page. For example, if you use the following startup parameters and run a .r file written with code page IBM850, Progress converts the text segments from ISO8859-1 to ibm861. This can produce incorrect results, if the .r file was correctly labeled internally as IBM850:
-cprcodein ISO8859-1 -cpinternal ibm861

To retrieve the value of this startup parameter at runtime, use the SESSION system handle. To determine the code page of an r-code file, use the RCODE-INFO handle.

437

R-code Out Code Page (-cprcodeout)

R-code Out Code Page (-cprcodeout)

Operating system and syntax Use with CS
code-page

UNIX Windows Maximum value Minimum value

-cprcodeout code-page

Single-user default -cpinternal

Multi-user default -cpinternal

Name of the code page for writing r-code text segments. Use R-code Out Code Page (-cprcodeout) to direct Progress to use the code page you specify to mark and convert text segments (any translatable text) when it writes r-code. If you do not specify -cprcodeout, Progress uses the code page you specify with Internal Code Page (-cpinternal) to write r-code. Typically, you do not need to specify this parameter since Progress converts the text segment to the -cpinternal code page when reading r-code. If the code page of the intended user is known, however, you can use this parameter to provide r-code in the users code page. Performance savings are not significant. To retrieve the value of this startup parameter at runtime, use the SESSION system handle. To determine the code page of an r-code file, use the RCODE-INFO handle.

438

Stream Code Page (-cpstream)

Stream Code Page (-cpstream)

Operating system and syntax Use with CS, DBS, DS, OID
code-page

UNIX Windows Maximum value Minimum value

-cpstream code-page

Single-user default ibm850

Multi-user default ibm850

Name of the code page for stream I/O. Use Stream Code Page (-cpstream) to identify the code page Progress uses for stream I/O. Character terminals use the code page you specify for -cpstream unless you also specify a value for Terminal Code Page (-cpterm), Print Code Page (-cpprint), or Log File Code Page (-cplog). Stream I/O consists of the following elements: Terminals (includes character terminals and DOS Protected mode, but does not include graphical interfaces or the Windows character interface). Data (.d) files.
READ-FILE, WRITE-FILE, INPUT FROM

and INSERT-FILE methods for the EDITOR widget.

and OUTPUT TO statements.

All compilable files (.p, .w, .i, and so on). Compiler-generated LISTING, XREF, and PREPROCESS files.

Note: Do not use a 7-bit table with -cpstream. Use 7-bit tables for converting data from a 7-bit terminal to another code page only. Do not use them for character conversion in memory or for the database. To retrieve the value of this startup parameter at runtime, use the SESSION system handle. To determine the code page of an r-code file, use the RCODE-INFO handle.

439

Terminal Code Page (-cpterm)

Terminal Code Page (-cpterm)

Operating system and syntax Use with CS, DBS, DS, OID
code-page

UNIX Windows Maximum value Minimum value

-cpterm code-page

Single-user default -cpstream

Multi-user default -cpstream

Name of the code page for character terminals. Use Terminal Code Page (-cpterm) to identify the code page of your character terminals. This parameter allows you to specify a different code page for character terminals than used by the rest of stream I/O, which is set by Stream Code Page (-cpstream). Note: You can use a 7-bit table with -cpterm. To retrieve the value of this startup parameter at runtime, use the SESSION system handle. To determine the code page of an r-code file, use the RCODE-INFO handle.

440

Cursor Size (-cs)

Cursor Size (-cs)

Operating system and syntax Use with CC
n

UNIX Windows Maximum value 256 Minimum value 1

-cs n

Single-user default 6

Multi-user default 6

The cursor size, which is the number of index levels. Use Cursor Size (-cs) to change the maximum number of index levels. You seldom need to use this parameter. Progress indexes have a tree structure. Even large indexes typically are no deeper than three or four levels. Index cursors, which act as place holders during file access, have size 6 by default; that is, they support up to five levels of indirect access. Therefore, few users ever require the cursor size (-cs) parameter. However, in rare cases involving large index keys, increase -cs in response to the following error message:

Index index-number has at least n levels. Increase -cs parameter.

Increasing -cs by 2 should be sufficient.

441

Directory Size (-D)

Directory Size (-D)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value 500 Minimum value 5

-D n

Single-user default 100

Multi-user default 100

The number of compiled procedure directory entries. Use Directory Size (-D) to change the number of compiled procedure directory entries. Each compiled procedure executed during an OpenEdge session requires a directory entry. A compiled procedure can be a session-compiled version of a procedure or a precompiled r-code version. When Progress creates a session-compiled version of a procedure and there is no available space in the directory, it discards the oldest inactive compilation of a procedure. The next time the discarded procedure is run, Progress must recompile it if it was a session compile, or reopen and reread it if it was a precompiled r-code version. The -D limit is a soft limit. If your application needs to exceed the limit, Progress automatically increases the number of directory entries by 50 percent and dynamically allocates memory for the expanded array. (Use the Statistics (-y) parameter to check the current directory size (-D) value. If the amount of memory necessary for allocating the expanded array is exceeded or if the size of the expanded array exceeds 31K, Progress exits the session.) When the limit is reached, Progress issues a WARNING message, which is written to the current output (if there is current output) and to the log file (LG). You can force Progress to adhere to the specified directory size (-D) limit by starting the session with the Hardlimit (-hardlimit) startup parameter. When you use the -hardlimit startup parameter, Progress issues a WARNING message when you exceed the directory size limit. It also issues a message that a resource limit was reached and raises an untrappable STOP condition. Note that -hardlimit also enforces the limits set by the Local Buffer Size (-l), the Maximum Memory (-mmax), and the Nested Blocks (-nb) startup parameters, so the STOP condition is raised when any of the specified limits are reached.

442

Date Format (-d)

Date Format (-d)

Operating system and syntax Use with CS
dateform

UNIX Windows Maximum value Minimum value

-d dateform

Single-user default mdy

Multi-user default mdy

The format used to display dates in an application. Use Date Format (-d) to specify the format used to display dates in an application using a three-character string of the letters: d, m, and y in any order. Note that -d sets the display format and not the storage format, which is fixed. Note also that the date constants entered in procedures, or as initial values in the Data Dictionary, are always specified in month/day/year format. This startup parameter provides the same functionality as the SESSION:DATE-FORMAT attribute.

443

DataService (-DataService)

DataService (-DataService)
Operating system and syntax Use with CC
data-service

UNIX Windows Maximum value

-DataService data-service

Minimum value

Single-user default

Multi-user default

The name of the DataService. Use DataService (-DataService) to connect through a NameServer to an ODBC or ORACLE DataServer. The value for data-service must be a valid name from the DataService list registered to this NameServer, as defined by your appServiceName List entry in the broker properties file. If a default DataService has been defined for your broker instance, you can omit this parameter and connect using the default service.

444

Physical Database Name (-db)

Physical Database Name (-db)

Operating system and syntax Use with CC
physical-dbname

UNIX Windows Maximum value Minimum value

-db physical-dbname

Single-user default

Multi-user default

The database to connect to when an OpenEdge session is started. Specify the physical (not the logical) database name. If you are connecting in single-user mode or through shared memory, and the database is not in your current directory, you must specify the full path of the database. Use Physical Database Name (-db) to connect one or more OpenEdge databases. Use Single-user Mode (-1) after the name of the database to connect in single-user mode. You do not have to precede the first database on the command line with -db; however, for all subsequent databases that you want to connect, precede the database name with -db. For example, the following command connects two databases, abc and xyz:

pro abc -B 30 -db xyz -B 40

445

Debugger (-debug)

Debugger (-debug)
Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-debug

Single-user default

Multi-user default

Use Debugger (-debug) to start an OpenEdge session by running the Application Debugger in stand-alone mode. This makes the Debugger (not the Procedure Editor) the point of entry for all application procedures to run. The Debugger begins by allowing breakpoints before using the Debugger RUN command to execute the startup procedure. Also, Progress automatically sets a breakpoint on the first executable line of the startup procedure before it runs. For more information on the Debugger, see OpenEdge Development: Debugging and Troubleshooting.

446

Debug Alert (-debugalert)

Debug Alert (-debugalert)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-debugalert

Single-user default

Multi-user default

You can use the -debugalert startup parameter along with the Client Logging (-clientlog) startup parameter to access 4GL stack trace information during a session. If you set -debugalert to yes, and use the -clientlog startup parameter to specify a log file name, the 4GL stack trace is written to the log file you specify with -clientlog. Messages are written to the log file as they are encountered during a session. This applies to both batch and interactive sessions. For WebSpeed and AppServer applications, the output goes to their respective log files. The stack trace is included only for the error messages and 4GL Alert-box messages that are normally written to the file specified with -clientlog. Note: If you do not use the -clientlog startup parameter to specify a log file, the messages are not written to a log file. When -debugalert is set to yes and an error occurs in a batch session for: A 4GL batch client, Progress records the 4GL stack trace information in the log file specified with -clientlog. In this case, Progress lists the stack trace information in reverse order. That is, the procedure that generated the error is written first, and the root procedure is written last. An AppServer client or a WebSpeed agent, Progress records the 4GL stack trace information in their respective log files, also in reverse order. If you view one of these log files in the Progress Explorer, it appears in top-down order since Explorer displays log files in reverse order.

447

Debug Alert (-debugalert) To retrieve or reset the value of this parameter at runtime, use the DEBUG-ALERT attribute of the SESSION system handle. For more information on the DEBUG-ALERT attribute or the SESSION system handle, see OpenEdge Development: Progress 4GL Reference.

448

Enable Attachable Debugging (-debugReady)

Enable Attachable Debugging (-debugReady)

Operating system and syntax Use with CS
port-number

UNIX Windows Maximum value

-debugReady

{ 0 | port-number }
Multi-user default

Minimum value

Single-user default

The port on which Progress opens a socket for connecting to the attachable Debugger. If you want Progress to find an available port, enter 0 (zero). The default value is 0. Use Enable Attachable Debugging (-debugReady) to enable a Progress process (that is, a Progress 4GL client, a single WebSpeed agent, or single AppServer process) to be attached to by the Debugger. A 4GL developer can attach the attachable Debugger to any Progress session running locally or remotely in a LAN environment. This allows the developer to run the Debugger on one machine and debug a Progress process running on another machine. You cannot specify both the Debugger (-debug) and Enable Attachable Debugging (-debugReady) startup parameters on the command line at the same time. If you do, Progress generates an error and shuts down. For more information about the attachable Debugger, see OpenEdge Development: Debugging and Troubleshooting.

449

Dictionary Expressions (-dictexps)

Dictionary Expressions (-dictexps)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-dictexps

Single-user default

Multi-user default

Use Dictionary Expressions (-dictexps) to specify that Progress uses dictionary and help validation for all fields in all frames when you compile an application. Progress continues compiling even after it encounters a validation error. This parameter serves as a temporary step to close possible validation holes in existing applications. It has the effect of adding a USE-DICT-EXPS option to every frame in the application, including those that are not used for input. This parameter closes all possible validation holes, but it is highly inefficient. You can override this functionality for a particular frame by using the NO-VALIDATE keyword for that frame. See the Frame Phrase reference entry in OpenEdge Development: Progress 4GL Reference for more details on the NO-VALIDATE option. If you do not specify -dictexps, Progress uses dictionary and help validation for a field only if that field is used in an UPDATE, SET, PROMPT-FOR, or ENABLE statement. In addition, Progress does not use dictionary and help validation when compiling if you specify only the widget:SENSITIVE=YES construct to make a widget sensitive. Progress stops compiling when it encounters a validation error.

450

Direct I/O (-directio)

Direct I/O (-directio)

Operating system and syntax Use with CC, DBS UNIX Windows Maximum value Minimum value

-directio

Single-user default Not enabled

Multi-user default Not enabled

Use Direct I/O (-directio) to open all files in unbuffered mode, which enables Progress to use an I/O technique that bypasses the operating system buffer pool and transfers data directly from a buffer to disk. This technique has several advantages over buffered reads and writes such as avoiding the overhead of maintaining the operating system buffer pool and eliminating competition for operating system buffers between Progress programs and other programs. The operating system buffer-pool algorithms are designed for efficient sequential file access; the Progress buffer-pool algorithms are more efficient for access to an OpenEdge database. You might improve Progress performance by using the direct I/O feature. To use direct I/O, use Blocks in Database Buffers (-B) to increase the size of the Progress buffer pool, since Progress I/O does not pass through the operating system buffer pool. Also, decrease the size of the operating system buffer pool to compensate for the additional memory allocated to Progress. Note: Use asynchronous page writers (APWs). They improve database performance by performing overhead operations in the background.

451

DataServer (-Dsrv)

DataServer (-Dsrv)
Operating system and syntax Use with DS
keyword ( , value)

UNIX Windows Maximum value

-Dsrv keyword ( , value)

[,
Minimum value

keyword2 ( , value2 )

... ]
Multi-user default

Single-user default

, keyword2 ( , value2 )

... ]

Parameters, with optional values, for DataServers. Use DataServer (-Dsrv) to tell OpenEdge that the specified keywords are parameters for the ODBC, ORACLE, or MS SQL Server DataServer. These parameters are specific to ODBC data sources or are required to connect to certain data sources using the OpenEdge DataServers. You can specify up to 50 keywords with the -Dsrv parameter. There are three types of DataServer parameters: OpenEdge DataServer for ODBC parameters. ODBC SQL connection and statement parameters. OpenEdge DataServer for ORACLE parameters.

For more information about the parameters, see the OpenEdge DataServer guides.

452

Database Type (-dt)

Database Type (-dt)

Operating system and syntax Use with CC, DS
db-type

UNIX Windows Maximum value Minimum value

-dt db-type

Single-user default Progress

Multi-user default Progress

The database type. Use Database Type (-dt) to specify one of the following database types: Progress, ODBC, ORACLE, and AS/400. The value is not case sensitive. When connecting to a non-OpenEdge database, use Database Type (-dt) to specify the type of database.

453

European Numeric Format (-E)

European Numeric Format (-E)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-E

Single-user default AMERICAN

Multi-user default AMERICAN

Use European Numeric Format (-E) parameter to tell Progress to display thousands separators as periods and decimal points as commas (for example: 1.234.567,89) when displaying or prompting for numeric values.
AMERICAN is the default value, in which periods are displayed as decimal points and commas as thousands separators (for example: 1,234,567.89).

When you specify EUROPEAN, continue to use periods as decimal points and commas as thousands separators in your source files. Note there is no command line parameter to specify AMERICAN, or reset EUROPEAN. Numeric format specifications in the Data Dictionary and the decimal constants in procedures always must use the period to represent the decimal point. You can also use the to get or set the numeric format.

454

Event Level (-evtlevel)

Event Level (-evtlevel)

Operating system and syntax

Windows Maximum value Minimum value

-evtlevel value

Use with CS, DBS

value

Single-user default Normal

Multi-user default Normal

Use Event Level (-evtlevel) to specify the level of information that OpenEdge writes to the Windows Application Event Log. Valid values include: None: No Progress events are written to the Event Log. Brief: OpenEdge Error and Warning messages are written to the Event Log. Normal: OpenEdge Error and Warning messages are written to the Event Log along with any OpenEdge message that is normally written to the log file (.lg). This is the default. Full: OpenEdge Error, Warning, and Informational messages are written to the Event Log along with any messages generated by the Message Statement.

For more information about OpenEdge and the Windows Event Log, see OpenEdge Getting Started: Installation and Configuration for UNIX and OpenEdge Getting Started: Installation and Configuration for Windows.

455

Expand Browse (-expandbrow)

Expand Browse (-expandbrow)

Operating system and syntax Use with CS

Windows Maximum value Minimum value

-expandbrow

Single-user default

Multi-user default

The -expandbrow startup parameter turns on the EXPANDABLE and FIT-LAST-COLUMN options for all browsers created in the current session. The EXPANDABLE attribute has the same behavior as the FIT-LAST-COLUMN attribute. Therefore, if the -expandbrow parameter is specified at startup, the FIT-LAST-COLUMN attribute is set to TRUE for each browse in that session. Note: Progress recommends that you use the FIT-LAST-COLUMN attribute instead of the EXPANDABLE attribute. This recommendation includes replacing EXPANDABLE with FIT-LAST-COLUMN in your current code. For more information on these attributes, see OpenEdge Development: Progress 4GL Reference.

456

Force Access (-F)

Force Access (-F)

Operating system and syntax Use with CC UNIX Windows Maximum value Minimum value

-F

Single-user default

Multi-user default

Use Force Access (-F) with the PROSHUT command to invoke an emergency shutdown of a shared-memory database. Note: The PROMON and PROUTIL utilities also use a -F parameter; however, the results are not the same. In addition, using -F with PROUTIL may compromise the integrity of the database. For more information, see OpenEdge Data Management: Database Administration.

457

Schema Field Cache Size (-fc)

Schema Field Cache Size (-fc)

Operating system and syntax Use with CS
num-entries

UNIX Windows Maximum value Minimum value 0

-fc num-entries

Single-user default 128

Multi-user default 128

The number of entries in the schema field cache. Use Schema Field Cache Size (-fc) to change the number of entries in the schema field cache. For example, you might increase the size if you retrieve large numbers of fields from your database. The Progress schema field cache reduces the time required to compile SQL queries by storing schema field information in memory. For best results, set this parameter to the total number of fields retrieved from the database. Progress uses approximately 150 additional bytes of memory per schema field cache entry used. Because memory is allocated when required, unused entries produce minimal overhead. If you set the value to 0, Progress disables schema field caching.

458

Filtering Asynchronous COM Events (-filterocxevents)

Filtering Asynchronous COM Events (-filterocxevents)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-filterocxevents

Single-user default

Multi-user default

The filterocxevents startup parameter, lets you control the conditions under which you want asynchronous COM events handled. An asynchronous COM event is one that is sent by an ActiveX control or Automation object because of an external event, rather than in response to user input. One example of this is the Tick event from the PSTimer. Another is an event signalling the receipt of a message from an external source, such as a control that implements a mail notification system. 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 WAITFOR or UPDATE statement. While an alert box from a MESSAGE statement is on the screen. During trigger processing, if the MultitaskingInterval parameter is set to a number greater than 0.

2. 3.

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.

459

Field List Disable (-fldisable)

Field List Disable (-fldisable)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-fldisable

Single-user default

Multi-user default

Use Field List Disable (-fldisable), which is a run-time parameter, to cause Progress to ignore field lists in the r-code and fetch complete records. For more information about using field lists, see OpenEdge Development: Progress 4GL Handbook.

460

Before-image Cluster Age (-G)

Before-image Cluster Age (-G)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value Minimum value 60

-G n

Single-user default

Multi-user default

The number of seconds Progress waits. Use Before-image Cluster Age (-G) to specify the number of seconds before Progress reuses a before-image cluster.

461

Group Delay (-groupdelay)

Group Delay (-groupdelay)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value 1,000 Minimum value 0

-groupdelay n

Single-user default 0

Multi-user default 1

The number of milliseconds a transaction waits before committing. Use Group Delay (-groupdelay) to increase performance when Delayed BI File Write (-Mf) is set to zero. When the Group Delay is set greater than zero (0), Progress uses a technique known as Group Commit. When using Group Commit, a transaction spools its end note to the BI buffer and waits a short time until the buffer becomes full and is written to disk, or waits for other transactions to end and store their end notes in the BI buffer so that several transactions are committed by the same synchronous write. In this manner, Group Commit benefits overall performance, although each individual transaction might take slightly longer.

462

Host Name (-H)

Host Name (-H)

Operating system and syntax Use with CC, DBS, DS
1

UNIX Windows (TCP) Maximum value

-H

host-name

| localhost1 }
Multi-user default

Minimum value

Single-user default

Localhost does not apply to DataServers.

host-name

The name (address) of the database server machine. This name is assigned to the machine in your TCP/IP hosts file.
localhost

A reserved word that specifies that the Database server communicate only with clients on the database server machine. Use Host Name (-H) to identify the host name.

463

Number of Databases (-h)

Number of Databases (-h)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value 240 Minimum value 1

-h n

Single-user default 5

Multi-user default 5

The maximum number of databases that can be connected during an OpenEdge session. Use Number of Databases (-h) to connect to more than five databases during a single OpenEdge session. Progress automatically allocates enough space to allow the connection of five databases.

464

Hardlimit (-hardlimit)

Hardlimit (-hardlimit)
Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-hardlimit

Single-user default

Multi-user default

Use Hardlimit (-hardlimit) to force Progress to adhere to the set limits for Directory Size (-D), Local Buffer Size (-l), Maximum Memory (-mmax), and Nested Blocks (-nb). These startup parameters are by default soft limits; that is, Progress tries to manage system resources within the limits given, but when it cannot, Progress increases the exceeded limit. When -hardlimit is specified and one of the limits is exceeded, Progress generates a WARNING message that is written to the current output (if there is current output) and to the log file (LG). In addition, Progress issues a message that a resource limit was reached and raises an untrappable STOP condition.

465

Hash Table Entries (-hash)

Hash Table Entries (-hash)

Operating system and syntax Use with CC, DBS
n

UNIX Windows Maximum value Minimum value 13

-hash n

Default Approximately 1/4 of the -B value.

The number of hash table entries to use for the buffer pool. Caution: Do not use this parameter unless directed to do so by Progress Software Technical Support.

466

No Crash Protection (-i)

No Crash Protection (-i)

Operating system and syntax Use with CC, DBS UNIX Windows Maximum value Minimum value

-i

Single-user default

Multi-user default

Use No Crash Protection (-i) to tell Progress to run without using database integrity or database recovery. When running Progress without database integrity, it writes fewer data and before-image blocks to the disk. In this mode, some Progress procedures (such as those that create and delete large numbers of records) run significantly faster than if they are running with database integrity. When running Progress with the -i parameter, transaction undo is supported. Therefore, there will still be a before-image file, which might grow quite large during very long transactions. Use this parameter to do bulk data loading or for large batch runs. It reduces the number of disk input or output operations. Loading a database for the first time is a good example of a use for this parameter. Caution: If you run Progress with the -i parameter and Progress fails for any reason, you cannot recover the database. Do not use the -i parameter unless you have a complete backup of the database and can rerun procedures in case of a system failure. If the system fails during an OpenEdge session started without crash protection, restore the backup copy and rerun the necessary procedures. For information on restoring a database, see OpenEdge Data Management: Database Administration.

467

No Crash Protection (-i) The following messages might appear when starting an OpenEdge session after a system failure: After a system failure while a full-integrity OpenEdge session was running:

**The last session was abnormally terminated. **Any incomplete transactions are being backed out. **Database recovery is complete. You must rerun all active transactions.

After a system failure while a no-integrity OpenEdge session was running:

**The last session was abnormally terminated. **The last session was run with the -i no integrity option. **Your database cannot be repaired, you must restore a backup copy.

468

Dynamics Parameter (-icfparam)

Dynamics Parameter (-icfparam)

Operating system and syntax Use with CS
string

UNIX Windows Maximum value Minimum value

-icfparam string

Single-user default

Multi-user default

A character string that supplies dynamics procedures with Dynamics-related data. Use the Dynamics (-icfparam) parameter to specify a character string that can be accessed from 4GL procedures within the Dynamics framework. You can access this string within a 4GL procedure by reading the ICFPARAMETER attribute of the SESSION system handle. Note: This parameter is reserved for use by Dynamics and procedures that have been integrated with Dynamics. Using this parameter for any purpose other than operating within the Dynamics framework will interfere with your ability to integrate your application with that framework at a later time. For more information on the ICFPARAMETER attribute or the SESSION system handle, see OpenEdge Development: Progress 4GL Reference.

469

Index Range Size (-indexrangesize)

Index Range Size (-indexrangesize)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value Minimum value

-indexrangesize n

Single-user default

Multi-user default

The number of indexes for which you want to track access statistics. Use Index Range Size (-indexrangesize) to specify the number of indexes for which you want to collect statistics. For more information on tracking index statistics, see OpenEdge Data Management: Database Administration.

470

Initialization File (-ininame)

Initialization File (-ininame)

Operating system and syntax Use with CS
name

Windows Maximum value Minimum value

-ininame name

Single-user default

Multi-user default

Name of the initialization registry subkey or the application's initialization (.INI) file. Use Initialization File (-ininame) to specify the location, in the registry, for the application's initialization information. When the Registry Base Key (-basekey) parameter is not specified at startup, Progress searches the HKEY_CURRENT_USER key followed by the HKEY_LOCAL_MACHINE key for the specified name. If no registry key of the specified name is found, Progress searches for a .INI file that matches name. You can only use this startup parameter at the command line. It is ignored when used in a .pf file. Note: The -ininame parameter replaces the -name option for the Windows Attributes (-Wa) parameter for Version 7.3B and later.

471

Input Characters (-inp)

Input Characters (-inp)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value 32,000 Minimum value 1

-inp n

Single-user default 4,096

Multi-user default 4,096

The number of characters allowed in a single statement. The default is 4,096 characters. Use Input Characters (-inp) to expand the available buffer space for a single statement. If not in use and 4,096 characters is exceeded in a statement, Progress displays a message stating that the statement is too long and advises you to increase the number of input characters using the -inp parameter.

472

AS/400 Ignore Stamp (-is)

AS/400 Ignore Stamp (-is)

Operating system and syntax Use with CC, DS UNIX Windows Maximum value Minimum value

-is

Single-user default

Multi-user default

Use Ignore Stamp (-is) to stop an OpenEdge client from comparing timestamps when attempting to connect an AS/400 database. When connecting to the schema holder database and the AS/400 database, Progress compares the timestamps on the files in the schema holder and the AS/400 physical and logical files. If the timestamps do not match, the login attempt is rejected. Note: Whenever any change to the AS/400 database structure is made (whether or not the change is saved), the AS/400 data dictionary time stamp changes. Progress checks the timestamp at the initial connection. If an AS/400 user modifies the file definitions after a successful Progress connect, the Progress user might get unpredictable results.

473

Initial Value Segment No Convert (-isnoconv)

Initial Value Segment No Convert (-isnoconv)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-isnoconv

Single-user default

Multi-user default

Use Initial Value Segment No Convert (-isnoconv) to disable a code page conversion that Version 9.1A provides and that previous versions do not. Consider using -isnoconv when all of the following conditions occur: A 4GL program contains character variables initialized from text literals. The text literals contain international characters (whether or not the literal is flagged as untranslatable using the :U attribute). The code page of the r-code (-cprcodein) does not match the code page of internal memory (-cpinternal). This is a compile-time option, not a run-time option, and affects the generation of r-code, not its execution.

When you run earlier versions of Progress under these conditions, and Progress reads text literals from r-code into internal memory, it does not convert the code page. To compensate for this, programmers often pre-convert international characters in text literals to -cpinternal. When you run Version 9.1A under these conditions, and Progress reads text literals from r-code into internal memory, it converts the code page from -cprcodein to -cpinternal. This code page conversion might cause international characters you have pre-converted to -cpinternal to be converted again to -cpinternal, which garbles them. Note: Progress Software Corporation recommends that you avoid preconverting text literals.

474

Keyword Forget List (-k)

Keyword Forget List (-k)

Operating system and syntax Use with CS
filename

UNIX Windows Maximum value Minimum value

-k filename

Single-user default

Multi-user default

The name of a file that contains OpenEdge keywords to disable. Each keyword must use a single line in the file. If OpenEdge encounters a word that is not an OpenEdge keyword, it returns a warning message but continues processing the file. OpenEdge uses the PROPATH variable to locate filename. If it cannot find filename, it displays an error message and does not start OpenEdge. Use Keyword Forget List (-k) to disable OpenEdge keywords. The keyword forget list is provided to ease migration from one release of OpenEdge to the next. Do not use keywords in procedures as object names (tables, fields, frames, variables, streams, and so on). If necessary, disable new keywords (and the features they implement) until they can be removed from the application. The directory where OpenEdge is installed contains the following keyword files:
newkywd,

which lists all keywords that are new in the most recent release of OpenEdge.

newkw810, which

you should use instead of newkywd, if you are converting from Progress Version 8 to OpenEdge Release 10. you should use instead of newkywd, if you are converting from Progress Version 7 to OpenEdge Release 10. you should use instead of newkywd, if you are converting from Progress Version 6 to OpenEdge Release 10. which you should use instead of newkywd, if you are converting from Progress Version 7 to Progress Version 9. which you should use instead of newkywd, if you converting from Progress Version 6 to Progress Version 9.

newkw710, which

newkw610, which

newkw79,

newkw69,

475

Key Alias (-keyalias)

Key Alias (-keyalias)

Operating system and syntax Use with DBS
key-alias-name

UNIX Windows Maximum value

-keyalias key-alias-name

Minimum value

Single-user default

Multi-user default default_server

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.

476

Key Alias Password (-keyaliaspasswd)

Key Alias Password (-keyaliaspasswd)

Operating system and syntax Use with DBS
1

UNIX Windows Maximum value

-keyaliaspasswd key-alias-password

Minimum value

Single-user default

Multi-user default password1

The actual value used is the encrypted value of the string password.

key-alias-password

Specifies the encrypted Secure Sockets Layer (SSL) Key Alias Password to use to access the servers 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 installations bin directory, to encrypt the password.

477

Lock Table Entries (-L)

Lock Table Entries (-L)

Operating system and syntax Use with DBS UNIX Windows Maximum value System dependent1 Minimum value 32

-L n

Single-user default

Multi-user default 8192

Limited by available memory.

The number of entries in the record locking table. If you specify a value that is not a multiple of 32, Progress rounds the value you specify to the next highest multiple of 32. Use Lock Table Entries (-L) to change the limits of the record locking table. Each record that is accessed by any user takes one entry. This is true whether the record is accessed with SHARE-LOCK or EXCLUSIVE-LOCK. Increase the size of the lock table if the following message appears:

SYSTEM ERROR: Record lock table too small. Increase -L parameter.

This message also might indicate that a particular procedure should be restructured into smaller transactions or should be run in single-user rather than multi-user mode. When lock table limits are exceeded, check to make sure transactions are not too large before increasing the lock table size. If a user process tries to acquire a lock and the lock table overflows, the user's program is aborted, but the server continues to operate. Any partial transactions are undone. Note that two record locks are acquired when records are accessed with the BREAK BY option (in DO, FOR EACH, or REPEAT statements). Each lock table entry takes 18 bytes on typical systems, but 14 bytes on nonshared-memory systems.

478

Local Buffer Size (-l)

Local Buffer Size (-l)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value 4,000,000,000 Minimum value 1

-l n

Single-user default 200

Multi-user default 200

The size of the local record buffer in 1KB units. Use Local Buffer Size (-l) to change the size of the local record buffer in which Progress stores all variables, work files, and records that are in use at one time for a user. The maximum size of the local record buffer is 4GB for most systems. If you get one of the following error messages, you need to increase the size of this buffer:

SYSTEM ERROR: bfget: No space. Increase -l parameter. SYSTEM ERROR: bfxpnd: No space. Increase -l parameter.

The Local Buffer Size (-l) limit is a soft limit; so if your application needs to exceed the limit, Progress automatically increases it and issues a WARNING message. The WARNING is written to the current output (if there is current output) and to the log file (LG). You can force Progress to adhere to the specified -l limit by starting the session with the Hardlimit (-hardlimit) startup parameter. When you use the -hardlimit startup parameter, Progress, issues the WARNING message when you exceed the Local Buffer Size limit. It also issues a message that a resource limit was reached and raises an untrappable STOP condition. Note that -hardlimit also enforces the limits set by the Directory Size (-D), the Maximum Memory (-mmax), and the Nested Blocks (-nb) startup parameters, so the STOP condition is raised when any of the specified limits is reached.

479

Logical Database Name (-ld)

Logical Database Name (-ld)

Operating system and syntax Use with CC
logical-dbname

UNIX, Windows Maximum value Minimum value

-ld logical-dbname

Single-user default

Multi-user default

The logical database name. Use Logical Database Name (-ld) to assign the logical name to a database. If you omit this parameter, Progress uses the physical database name (without the path or .db suffix). The name must be a valid identifier, which means: It can be up to 32 characters long. It can be any combination of English letters and numbers, underscore (_), and dash (-) characters. The first character must be an uppercase or lowercase letter.

A logical database name cannot include Progress 4GL reserved words, a space, any accented letters, or the following special characters:

\ "

'

<

>

For more information on logical database names, see OpenEdge Development: Progress 4GL Handbook and OpenEdge Data Management: Database Administration.

480

Lock Timeout (-lkwtmo)

Lock Timeout (-lkwtmo)

Operating system and syntax Use with CS
1

UNIX Windows Maximum value Minimum value 60

-lkwtmo seconds

Single-user default 18001

Multi-user default 18001

The default wait time for WebSpeed is 10 seconds.

seconds

The wait time, in seconds. Use Lock Timeout (-lkwtmo) to specify a different wait time (in seconds). An OpenEdge process encountering a locked resource waits for a limited time before continuing execution. If the resource is still locked, the process times out and the wait is canceled. This feature is called lock wait timeout. The default wait time is 1800 seconds (30 minutes). The minimum value is 60 seconds. If a user specifies a value less than 60 seconds, Progress silently sets the value at 60 seconds. Note: The wait time is accurate to within one minute of the value specified. Lock timeout applies to interactive and batch clients. Lock timeout affects WAIT-FOR record locks, schema locks, and transaction commit locks. Lock timeout does not affect internal locks used inside the database manager, such as buffer locks.

481

Language (-lng)

Language (-lng)
Operating system and syntax Use with CS
language-name

UNIX Windows Maximum value Minimum value

-lng language-name

Single-user default ?

Multi-user default ?

A character string that contains the name of the current language. This value must be surrounded by quotes. Use Language (-lng) to specify the initial return value for the CURRENT-LANGUAGE function. This setting determines from which r-code segment Progress reads character-string constants. The default value for the Language parameter is a character string that contains the question mark (?) character, which is not to be confused with the unknown value. This tells Progress to use the default language for the application. For more information on the Language startup parameter, see OpenEdge Development: Internationalizing Applications and OpenEdge Development: Progress 4GL Reference.

482

Log Entry Types (-logentrytypes)

Log Entry Types (-logentrytypes)

Operating system and syntax Use with CS
string

UNIX Windows Maximum value Minimum value

-logentrytypes string

Single-user default

Multi-user default

A character string that specifies a comma-separated list of log entry types. Use Log Entry Types (-logentrytypes) to specify one or more types of log entries to write to the log file specified by the Client Logging (-clientlog) startup parameter. 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]

log-entry-type

A log entry type listed in Table 41 below.

level

A logging level value (between 0 and 4).

483

Log Entry Types (-logentrytypes) Table 41 describes the log entry types. Table 41: Log entry types Executable 4GL (GUI and character mode). AppServer and WebSpeed do not require this log entry type for 4GL messages to be written to the log file. Description The 4GL interpreter writes all 4GL VIEW-AS ALERT-BOX messages to the log file, together with the 4GL stack, when you turn on Debug Alert, using either the -debugalert startup parameter or the SESSION system handle. Turns on logging of the execution of the following 4GL statements: RUN, PUBLISH, FUNCTIONS, SUBSCRIBE, and user-defined functions. Turns on logging for the AIA component. (1 of 2)

Log entry type

4GLMessages

4GLTrace

4GL clients, AppServer, and WebSpeed servers.

AiAMgmt AiaProp AiaRqst AiaUbroker AiaDefault ASDefault

AIA.

AppServer server.

Combines the AsPlumbing and DB.Connects log entry types. It is the default value for AppServer servers. Turns on logging for different actions, depending on the logging level specified. Turns on logging of database connections and disconnections. The messages include database name and user ID number.

ASPlumbing

AppServer server.

DB.Connects

4GL clients, AppServer, and WebSpeed agents.

484

Log Entry Types (-logentrytypes) Table 41: Log entry types Executable 4GL clients, AppServer, and WebSpeed agents. Description Turns on logging for creation and deletion of dynamic objects. (2 of 2)

Log entry type

DynObjects.DB DynObjects.XML DynObjects.Other

DynObjects.UI

4GL clients and WebSpeed agents. 4GL clients, AppServer, and WebSpeed agents. Turns on logging for file opening, file closing, and error messages that do not contain the file number. Turns on logging for WebSpeed Messengers. The information logged depends on which Messenger is running and the logging level specified. Turns on logging for the NameServer component. Turns on event logging for different categories of events. Turns on logging of query resolution statistics. Turns on logging for the SAX parser. Turns on logging for the Unified Broker component.

FileID

MsgrTrace

WebSpeed Messengers.

NSPlumbing

NameServer. 4GL clients, AppServer, and WebSpeed agents. 4GL clients, AppServer, and WebSpeed agents. 4GL clients, AppServer, and WebSpeed agents. Unified Broker.

ProEvents.UI.Char ProEvents.UI.Command ProEvents.Other QryInfo

SAX

UBroker.Basic UBroker.ClientFSM UBroker.ServerFSM UBroker.ClientMsgStream UBroker.ServerMsgStream UBroker.ClientMsgQueue UBroker.ServerMsgQueue UBroker.ClientMemTrace UBroker.ServerMemTrace UBroker.ThreadPool UBroker.Stats UBroker.AutoTrim UBroker.All

485

Log Entry Types (-logentrytypes) For more information about log entry types, see OpenEdge Development: Debugging and Troubleshooting. The following example shows how to specify one or more individual log entry types:

-logentrytypes DB.Connects,4GLTrace:2,DynObjects.UI:3

The following example shows how to specify all log entry types within a category:

-logentrytypes DynObjects.*

For more information about logging levels and log entry types, see OpenEdge Development: Debugging and Troubleshooting. You also can turn on logging at run-time by using the LOG-ENTRY-TYPES attribute on the
LOG-MANAGER system handle. For example, you can include the following line in your 4GL code:

LOG-MANAGER:LOG-ENTRY-TYPES = "DynObjects.UI"

You can turn off logging in your 4GL code by setting this attribute to the Unknown value (?). For example:

LOG-MANAGER:LOG-ENTRY-TYPES = ?

For more information about the LOG-ENTRY-TYPES attribute or the LOG-MANAGER system handle, see the OpenEdge Development: Progress 4GL Reference.

486

Logging Level (-logginglevel)

Logging Level (-logginglevel)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value Minimum value

-logginglevel n

Single-user default

Multi-user default

A logging level value (between 0 and 4). Use Logging Level (-logginglevel) to specify the level at which log entries are written to the log file specified by the Client Logging (-clientlog) startup parameter. Each logging level specifies a different amount of information. Logging level represents the amount of logging information written to the log file, as shown in Table 42. Table 42: Logging levels Description Log no entries. This is equivalent to turning logging off. Log OpenEdge error messages. This includes all error messages and is unrelated to the entry types specified. Errors continue to be logged at all higher levels. Log entry types determine the logged information. Each entry type will generate at least some output. This is the default. Log entry types determine the logged information. Log entry types determine the logged information.

Logging level 0 (None) 1 (Errors)

2 (Basic) 3 (Verbose) 4 (Extended)

By default, the logging level you specify applies to all log entry types. However, you can specify individual log entry types with a different logging level using the Log Entry Types (-logentrytypes) startup parameter.

487

Logging Level (-logginglevel) You can also use attributes on the LOG-MANAGER system handle to specify log entry types and logging levels. For more information, see the OpenEdge Development: Progress 4GL Reference. For more detailed information about enabling logging, see OpenEdge Development: Debugging and Troubleshooting.

488

Log Threshold (-logthreshold)

Log Threshold (-logthreshold)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value Minimum value

-logthreshold n

Single-user default

Multi-user default

A log file size threshold. 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. Valid values are: 0 This means there is no limit other than what the operating system imposes. Specify 0 to ignore the Number of Log Files to Keep (-numlogfiles) startup parameter setting. This is the default. Between 500,000 and 2,147,483,647 Values are in bytes (one byte typically holds one character). You can specify a file size up to 2GB, inclusive, but not lower than 500,000. If you specify a number lower than 500,000, a run-time error occurs and the OpenEdge process terminates. OpenEdge names log files based on a sequence number using the following format:

<filename>.999999.<extension>

For example, if you specify a log file named my.log, OpenEdge renames the log file to my.000001.log before creating a new log file.

489

Log Threshold (-logthreshold) Use the Client Logging (-clientlog) startup parameter to specify a log file name for 4GL clients. Use the Number of Log Files to Keep (-numlogfiles) startup parameter to specify the number of log files to keep. You can also can use the LOG-THRESHOLD attribute on the LOG-MANAGER system handle to specify the file size threshold of log files. For more information, see the OpenEdge Development: Progress 4GL Reference.

490

Auto Server (-m1)

Auto Server (-m1)

Operating system and syntax Use with DBS UNIX Windows Maximum value Minimum value

-m1

Single-user default

Multi-user default

Use Auto Server (-m1) to start an auto server. The OpenEdge broker uses the auto server internally to start a remote user server. This is the default. You will never have to use this parameter directly.

491

Manual Server (-m2)

Manual Server (-m2)

Operating system and syntax Use with DBS UNIX Windows Maximum value Minimum value

-m2

Single-user default

Multi-user default

Use Manual Server (-m2) to manually start a remote user server after you start a broker (servers are generally started automatically by the broker process). Use this parameter in the following cases: For debugging purposes, to start servers directly and observe their behavior. On systems where automatic server generation is not possible.

492

Secondary Login Broker (-m3)

Secondary Login Broker (-m3)

Operating system and syntax Use with DBS UNIX Windows Maximum value Minimum value

-m3

Single-user default

Multi-user default

In a network environment where more than one broker is using the same protocol, use Secondary Login Broker (-m3) to start each secondary broker. The secondary broker logs in clients and starts remote user servers.

493

Maximum Clients Per Server (-Ma)

Maximum Clients Per Server (-Ma)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value 2048 Minimum value 1

-Ma n

Single-user default

Multi-user default 5 users/server

The maximum number of remote users per database server. The default is the Maximum Number of Users (-n) parameter value, divided by the Maximum Number of Servers (-Mn) parameter value. Use Maximum Clients per Server (-Ma) to specify the maximum number of remote users per database server. The Maximum Clients per Server (-Ma), Minimum Clients per Server (-Mi), and Maximum Servers (-Mn) startup parameters pertain only to versions of Progress that use shared memory. In addition, these parameters apply only to databases that are accessed from remote network nodes. In most cases, the default behavior is desirable. Note that the default calculation is usually high because it assumes that all users are remote users, while the number specified with -n includes local users. If servers become overloaded with clients, reset the -Mn parameter to increase the number of servers. If experience proves that a given number of remote clients overloads a server or exhausts the file descriptors on the system, set -Ma to limit clients per server below that level. A file descriptor is an object UNIX uses to identify a particular file. The file descriptors might be exhausted because Progress uses them to identify sockets.

494

Maximum Dynamic Server (-maxport)

Maximum Dynamic Server (-maxport)

Operating system and syntax Use with DBS UNIX Windows Maximum value System dependent Minimum value System dependent

-maxport n

Single-user default

Multi-user default 2000

The port number that is the highest in a specified range. Use Maximum Dynamic Server (-maxport) to specify the highest port number in a specified range of port numbers accessible to a client. You specify the lowest port number with the -minport parameter. The range of port numbers defined by the -maxport and -minport parameters provides client access to an OpenEdge server that is behind a firewall. Some operating systems choose transient client ports in the 32,768-to-65,535 range. Choosing a port in this range might produce unwanted results.

495

Delayed BI File Write (-Mf)

Delayed BI File Write (-Mf)

Operating system and syntax Use with DBS
1 2

UNIX Windows Maximum value 32,768 Minimum value 0

-Mf n

Single-user default 01

Multi-user default 32

Default is 3 for batch jobs. Default is 0 for nonshared-memory systems.

Any positive value delays Progress from synchronously writing out to disk the last before-image (BI) file records at the end of each transaction. On UNIX systems using shared memory, it also specifies the interval that the broker process wakes up to make sure all BI file changes have been written to disk. The default is 3 for single-user batch jobs and for multi-user databases using shared memory. Otherwise, the default is 0. Use Delayed BI File Write (-Mf) to improve performance on a heavily loaded system. Using -Mf does not reduce database integrity. However, if there is a system failure, it is possible the last few completed transactions will be lost (never actually written to the BI file). When running with full integrity, at the end of each transaction Progress does a synchronous write to disk of the last BI file block. This write guarantees that the completed transaction is recorded permanently in the database. If the user is notified that the transaction has completed and the system or database manager crashes shortly afterwards, the transaction is not lost. Do not set -Mf on a lightly loaded system with little database update activity. Under these conditions, the extra BI write is very important and does not impact performance. On a heavily loaded system, however, the BI write is less important (the BI block will be written to disk very soon anyway), and has a significant performance penalty. Setting -Mf to delay this extra BI write saves one write operation per transaction, which can significantly improve performance. The extra BI file write is delayed by default for batch jobs. If -Mf is set to a positive value, the last BI file record is only guaranteed to be written out to disk when a user logs out, or when the server or broker process terminates normally. On multi-user systems, the n argument determines the oldest completed transaction that can be lost.

496

Minimum Clients per Server (-Mi)

Minimum Clients per Server (-Mi)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value Minimum value 1

-Mi n

Single-user default

Multi-user default 1

The number of remote users on a server before the broker starts another server. See also the Maximum Servers (-Mn) startup parameter. Use Minimum Clients per Server (-Mi) to specify the number of remote users on a server before the broker starts another server (up to the maximum number of servers). This parameter pertains only to multi-user versions of Progress that use shared memory. In addition, -Mi and -Mn apply only to databases accessed from remote network nodes. As remote users enter the database, the broker process starts just one server process for each n remote users, until the maximum number of servers (specified by the -Mn parameter) is started. If you specify a value of 1, the broker starts a new server for each of the first -Mn remote users. Subsequent remote users are distributed evenly among the servers until the maximum number of users (-n) or maximum clients per server (-Ma) limits are reached. Typically, you can leave -Mi and -Mn at their default values. If you significantly increase -Mn, you should also increase -Mi. For example, if you set -Mn to 10 to accommodate up to 40 or more remote users, increase -Mi to 3 or 4 to prevent a situation where 10 servers were started for just 10 remote users.

497

Minimum Dynamic Server (-minport)

Minimum Dynamic Server (-minport)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value Minimum value 1,025

-minport n

Single-user default

Multi-user default 1,025

The port number that is the lower in a specified range. Use Minimum Dynamic Server (-minport) to specify the lowest port number in a specified range of port numbers accessible to a client. You specify the higher port number with the -maxport parameter. Ports below 1025 are usually reserved for system TCP and UDP. The range of port numbers defined by the -maxport and -minport parameters provides client access to an OpenEdge server that is behind a firewall. This communication is possible only when the access to the server can be limited.

498

Message Buffer Size (-Mm)

Message Buffer Size (-Mm)

Operating system and syntax Use with CC,DBS
n

UNIX Windows Maximum value 32,600 Minimum value 350

-Mm n

Single-user default

Multi-user default 1,024

The message buffer size. Use Message Buffer Size (-Mm) to specify the standard message buffer size, in bytes. This parameter is relevant only for network client/server connections. OpenEdge uses message buffers to move records (messages) between servers and remote clients. Records (plus 40-byte headers) larger than the message buffer size are fragmented into multiple messages. If your database records are large, increase this parameter to avoid record fragmentation. However, if the network works more efficiently with small messages, reduce -Mm and fragment larger records. Note: On a given database, you must specify the same message buffers size when starting the server or broker (using PROSERVE) and multi-user clients (using MPRO) and when shutting down the database (using PROSHUT). That is, if you change the -Mm value on any database command, you must change all PROSERVE command, MPRO command, and PROSHUT commands accordingly.

499

Maximum Memory (-mmax)

Maximum Memory (-mmax)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value 65,534 Minimum value 1

-mmax n

Single-user default 3,096

Multi-user default 3,096

The amount of memory allocated for r-code segments. Use Maximum Memory (-mmax) to change the initial amount of memory allocated for r-code segments, in kilobytes. Progress dynamically allocates space for r-code segments in the execution buffer as needed. When memory allocation reaches the value specified by the Maximum Memory (-mmax) value, Progress writes nonactive segments to the sort file to make room for new active procedures. (Progress writes library-stored r-code to the sort file only if you specified the PROLIB Swap (-pls) startup parameter.) If you have large procedures or deeply nested procedure calls, you can use -mmax to increase the initial size of the execution buffer to reduce disk I/O activity required to swap segments to the sort file. The -mmax value does not limit the amount of memory available for r-code segments. If Progress requires more space in the execution buffer and cannot regain enough space by swapping inactive segments to the sort file, Progress allocates more memory. The -mmax limit is a soft limit; so if your application needs to exceed the limit, Progress automatically increases it and issues a WARNING message. The WARNING is written to the current output (if there is current output) and to the log file (LG). You can force Progress to adhere to the specified -mmax limit by starting the session with the Hardlimit (-hardlimit) startup parameter. When you use the -hardlimit startup parameter, Progress issues the WARNING message when you exceed the Maximum Memory limit. It also issues a message that a resource limit was reached and raises an untrappable STOP condition. Note also that -hardlimit also enforces the limits set by the Directory Size (-D) the Local Buffer Size (-l), and the Nested Blocks (-nb) startup parameters. The STOP condition is raised when any of the specified limits is reached. Use Statistics (-y) and Segment Statistics (-yd) to see segment allocation information.

4100

Maximum Servers (-Mn)

Maximum Servers (-Mn)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value 512 Minimum value 1

-Mn n

Single-user default

Multi-user default 4

The maximum number of remote client servers that can be started on the system. Use Maximum Servers (-Mn) to limit the number of remote user servers that can be started by the broker process. The performance tradeoff to consider is swapping overhead for many servers versus overloading (slowing down) a server with too many clients. For more information on controlling memory use, see OpenEdge Data Management: Database Administration. This parameter pertains only to multi-user versions of Progress that use shared memory. In addition, this parameter applies only to databases that are accessed from remote network nodes. Also, use Minimum Clients per Server (-Mi) to adjust the actual number of servers in use. See the Maximum Clients Per Server (-Ma) and Minimum Clients per Server (-Mi) startup parameters for more information.

4101

Servers Per Protocol (-Mp)

Servers Per Protocol (-Mp)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value value of -Mn Minimum value 1

-Mp n

Single-user default

Multi-user default value of -Mn

The number of servers a broker can start. Use Servers per Protocol (-Mp) with Secondary Login Broker (-m3) in database networks that use more than one network protocol. This parameter limits the number of servers that the broker can start to serve remote users for any one protocol. The total number of servers for all protocols is still limited by the Maximum Servers (-Mn) parameter.

4102

Maximum Servers Per Broker (-Mpb)

Maximum Servers Per Broker (-Mpb)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value Minimum value

-Mpb n

Single-user default

Multi-user default

The number of servers multiple brokers can start. Use Maximum Server Per Broker (-Mpb) to specify the maximum number of servers that multiple brokers can start to serve remote users for any one protocol. For more information, see OpenEdge Data Management: Database Administration.

4103

VLM Page Table Entry Optimization (-Mpte)

VLM Page Table Entry Optimization (-Mpte)

Operating system and syntax Use with DBS

Digital UNIX Maximum value Minimum value

-Mpte

Single-user default

Multi-user default

Use VLM Page Table Entry Optimization (-Mpte) to allocate shared memory in multiples of 8MB at server startup for VLM64 support. This function is a binary switch that is off by default. The -Mpte startup parameter turns the function on.

4104

Record Buffer Size (-Mr)

Record Buffer Size (-Mr)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value 32,000 Minimum value 96

-Mr n

Single-user default

Multi-user default 1,012

The standard record buffer size in bytes. On some systems, you can use Record Buffer Size (-Mr) to improve performance by varying the standard record buffer size. However, the default value of 1,024 bytes is appropriate in nearly all cases. The record buffer size dictates that compaction or garbage collection is performed on the user's local buffer. If the largest contiguous fragment of free memory in the local buffer falls below the record buffer size in length, Progress automatically consolidates all free space. Free-space consolidation also occurs when your process attempts to read in a database record that is larger than the largest block of free space available. Consolidation is more expensive in this case, because the record-copying process is interrupted for free-space consolidation when the record does not fit, and the copying process must then be restarted. To avoid record recopying, set -Mr larger than the database record size (1,024 is larger than the records in most databases). The tradeoff is more occurrences of (less expensive) automatic free space consolidation.

4105

Shared-memory Overflow Size (-Mxs)

Shared-memory Overflow Size (-Mxs)

Operating system and syntax Use with DBS
1 2

UNIX Windows Maximum value Varies1 Minimum value 1

-Mxs n

Single-user default

Multi-user default Varies

The maximum is limited only by the size of the signed integer data type on the system. If your system uses a 4 byte integer, then the formula is: 16KB + (n*300). For all other systems, the formula is: 16KB + (n*400).

The size of the shared-memory overflow area in kilobytes. Use Shared-memory Overflow (-Mxs) to replace the default value of the shared-memory overflow area; it does not increase it. The overflow area is appended to the shared-memory area. This parameter is relevant only on shared-memory systems. If the overflow area is too small, OpenEdge exits with the following message:

SYSTEM ERROR: Out of free shared memory. Use -Mxs to increase.

Depending on the operating system, OpenEdge rounds the shared-memory area size to the next 512-byte or 4K boundary.

4106

Number of Users (-n)

Number of Users (-n)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value 10,000 Minimum value

-n n

Single-user default

Multi-user default 20

The maximum number of Progress users on the system. After n users have connected to the OpenEdge database, additional user startup attempts are rejected. On systems that do not use shared memory, use Number of Users (-n) to limit the total number of users below the level that overloads the database server. On shared-memory systems, -n must be high enough to include local and remote users as well as background writers (APWs, BIWs, and AIWs), PROWDOG processes, and PROMON sessions. For more information, see the Minimum Clients per Server (-Mi) and Maximum Servers (-Mn) startup parameters.

4107

Nested Blocks (-nb)

Nested Blocks (-nb)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value 255 Minimum value 20

-nb n

Single-user default 50

Multi-user default 50

The maximum number of nested blocks. Use Nested Blocks (-nb) to limit the maximum number of nested procedure blocks allowed. By default, the maximum number of nested blocks is 50. Nested block entries are allocated in memory; each requires 12 bytes. Therefore, decrease -nb only if memory is severely limited. The -nb limit is a soft limit; so if your application needs to exceed the limit, Progress automatically increases it and issues a WARNING message. The WARNING is written to the current output (if there is current output) and to the log file (LG). You can force Progress to adhere to the specified -nb limit by starting the session with the Hardlimit (-hardlimit) startup parameter. When you use the -hardlimit startup parameter, Progress, issues the WARNING message when you exceed the Nested Blocks (-nb) limit. It also issues a message that a resource limit was reached and raises an untrappable STOP condition. Note that -hardlimit also enforces the limits set by the Directory Size (-D), the Local Buffer Size (-l), and the Maximum Memory (-mmax) startup parameters, so the STOP condition is raised when any of the specified limits is reached.

4108

No Lock (-NL)

No Lock (-NL)
Operating system and syntax Use with CS, OID (Version 7.3B and later) UNIX Windows Maximum value Minimum value

-NL

Single-user default

Multi-user default

Use No Lock (-NL) to have all record retrieval statements default to NO-LOCK record access. In order to get the NO-LOCK default for any procedure, it must be compiled in an OpenEdge session started with -NL. Running OpenEdge with -NL has no affect on precompiled procedures. When a transaction ends, EXCLUSIVE locks are downgraded to SHARE-LOCK, regardless of the -NL parameter. For Version 7.3B and later, you can specify -NL as a startup parameter for the Open Interface Driver to support ODBC applications that perform multiple connections to the same data source, lock all records in a read table, or that otherwise exceed the lock table size with large databases.

4109

No Auto Result-list (-noautoreslist)

No Auto Result-list (-noautoreslist)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-noautoreslist

Single-user default

Multi-user default

Use No Auto Result-list (-noautoreslist) to avoid building result-lists for static non-scrolling queries. A static non-scrolling query is one that is: Defined using the DEFINE QUERY statement without the SCROLLING option. Opened using the OPEN QUERY statement (but not previously defined using the DEFINE statement).

QUERY

Not associated with a browse widget (and has not been changed into a scrolling query by the DEFINE BROWSE statement).

When you specify this startup parameter, you cannot use the GET PREV, GET LAST, REPOSITION, or BROWSE methods or statements with static non-scrolling queries. If you do, OpenEdge generates an error. You can use the GET-FIRST( ) method and GET FIRST statement only on newly opened queries, and you can use the GET NEXT statement and GET-NEXT( ) method freely. If you specify this startup parameter and you open a static non-scrolling query with preselect or sort, OpenEdge still builds a result-list in order to resolve the query. Specifying this startup parameter has no affect on dynamic queries, since they are scrolling queries by default. Specifying this startup parameter can improve the performance of operations on queries.

4110

No Check Temp-table Names (-nochkttnames)

No Check Temp-table Names (-nochkttnames)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-nochkttnames

Single-user default

Multi-user default

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. When passing temp-table as a parameter to a procedure, the calling procedures temp-table and the called procedures temp-table must match with respect to the number of columns, the data type of each column, and the number of extents of each column (for columns with extents). Progress provides limited checking of temp-table column names when passing temp-tables as parameters to procedures. That is, for any given column: If the name of a column in the calling procedures temp-table does not match any column defined in the called procedures temp-table, Progress processes the column. If the name and position of a column in the calling procedures temp-table matches a column defined in the called procedures temp-table, Progress processes the column. If the name of a column in the calling procedures temp-table matches a column defined in the called procedures temp-table, but the positions do not match, Progress reports an error and the called procedure does not run.

Use the No Check Temp-table Names (-nochkttnames) parameter when you want Progress to process the temp-table without verifying column names. Note: Temp-table column names are case-insensitive.

4111

No Host Verify (-nohostverify)

No Host Verify (-nohostverify)

Operating system and syntax Use with CC UNIX Windows Maximum value Minimum value

-nohostverify

Single-user default

Multi-user default

Use No Host Verify (-nohostverify) to turn off host verification for a Secure Sockets Layer (SSL) connection to a database server. Without this parameter specified, the client compares the host name specified in the connection with the Common Name specified in the server certificate, and raises an error if they do not match. With this parameter specified, the client never raises the error. For more information, see OpenEdge Getting Started: Security.

4112

Index Hint (-noindexhint)

Index Hint (-noindexhint)

Operating system and syntax Use with DS UNIX Windows Maximum value Minimum value

-noindexhint

Single-user default

Multi-user default

Use Index Hint (-noindexhint) to stop a DataServer for ORACLE from providing index hints to the ORACLE DBMS, which the DataServer does by default. Generally, index hints improve performance, but ORACLE's responses to hints varies among releases. This parameter is valid only when using the DataServer for ORACLE.

4113

Server Join (-nojoinbysqldb)

Server Join (-nojoinbysqldb)

Operating system and syntax Use with DS UNIX Windows Maximum value Minimum value

-nojoinbysqldb

Single-user default

Multi-user default

Use Server Join (-nojoinbysqldb) to specify that the client evaluate and performs queries that have joins. This might slow performance, but provides results that are consistent with Progress behavior. It also allows you to run DataServer applications on Version 9 clients with Version 8 servers. It overrides the DataServer default behavior, which is to instruct the non-OpenEdge server to perform the join. Use -nojoinbysqldb at compile time. It has no effect at run time.

4114

No Session Cache (-nosessioncache)

No Session Cache (-nosessioncache)

Operating system and syntax Use with DBS UNIX Windows Maximum value Minimum value

-nosessioncache

Single-user default

Multi-user default

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.

4115

No Session Reuse (-nosessionreuse)

No Session Reuse (-nosessionreuse)

Operating system and syntax Use with CC UNIX Windows Maximum value Minimum value

-nosessionreuse

Single-user default

Multi-user default

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. For more information, see OpenEdge Getting Started: Security.

4116

SELECT Pass Through Disable (-noSQLbyserver)

SELECT Pass Through Disable (-noSQLbyserver)

Operating system and syntax Use with DS UNIX Windows Maximum value Minimum value

-noSQLbyserver

Single-user default

Multi-user default

Use SELECT Pass Through Disable (-noSQLbyserver) to turn off SELECT Pass Through for the current OpenEdge session. Use with DataServers for ODBC and ORACLE.

4117

Fractional Separator (-numdec)

Fractional Separator (-numdec)

Operating system and syntax Use with CS
numeric-value

UNIX Windows Maximum value Minimum value

-numdec numeric-value

Single-user default . (period)

Multi-user default . (period)

The numeric value of the character that represents the decimal point. Use Fractional Separator (-numdec) to change the character that represents a numbers decimal point in formatted text. Progress converts numeric-value to its character equivalent using the code page corresponding to the Internal Code Page (-cpinternal) startup parameter. The decimal point cannot be represented by any of the following: The characters B C D R Z z 0 1 2 3 4 5 6 7 8 9 + - < > ( ) * ? The space character. Any multi-byte character.

As an example, to change the decimal point in formatted text to a comma (whose numeric value in the ISO8859-1 code page is 44), use:

-numdec 44

The default decimal point is the period (.).

4118

Number of Log Files to Keep (-numlogfiles)

Number of Log Files to Keep (-numlogfiles)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value Minimum value

-numlogfiles n

Single-user default 3

Multi-user default 3

The number of log files to keep. Use Number of Log Files to Keep (-numlogfiles) to specify the total number of rolled over log files to keep on disk at any one time, across OpenEdge sessions, including the current log file. Valid values are: 0 This means there is no limit on the number of log files to keep. 2 or greater The default is 3. If you specify a value of 1, a run-time error occurs and the OpenEdge process terminates. Use the Log Threshold (-logthreshold) startup parameter to specify the file size at which OpenEdge renames and saves log files. You also can use the NUM-LOG-FILES attribute on the LOG-MANAGER system handle to specify the number of log files to keep. For more information, see the OpenEdge Development: Progress 4GL Reference.

4119

Thousands Separator (-numsep)

Thousands Separator (-numsep)

Operating system and syntax Use with CS
numeric-value

UNIX Windows Maximum value Minimum value

-numsep numeric-value

Single-user default , (comma)

Multi-user default , (comma)

The numeric value of the character that represents the thousands separator. Use Thousands Separator (-numsep) to change the character that represents a numbers thousands separator in formatted text. Progress converts numeric-value to its character equivalent using the code page corresponding to the Internal Code Page (-cpinternal) startup parameter. The thousands separator cannot be represented by any of the following: The characters B C D R Z z 0 1 2 3 4 5 6 7 8 9 + - < > ( ) * ? Any multi-byte character.

Note: You can represent the thousands separator with the space character. As an example, to change the thousands separator in formatted text to an apostrophe (whose numeric value in the ISO8859-1 code page is 39), use:

-numsep 39

The default thousands separator is the comma (,).

4120

Printer (-o)

Printer (-o)
Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-o printername

Single-user default System dependent1

Multi-user default System dependent1

See defaults listed below.

printername

Identifies the printer to use when processing the OUTPUT TO PRINTER statement in procedures. On Windows: Use Printer (-o) followed by the name of the printer port. For example:

-o LPT1

If you do not use the -o parameter, Progress uses the printer specified as the default printer. On UNIX: Use Printer (-o) followed by the name of the spooler and any necessary parameters. If you do not use the -o parameter, Progress defaults to lp (System V) or lpr (BSD). If you are passing arguments with this parameter and are using a script such as PRO or one of your own, enclose the entire string in quotes so the argument to -o is returned as a single value when passed to the Progress module:

-o "lp -s"

Progress uses the spooler or printer port named at execution time rather than using the name at compile time. That way, precompiled procedures work regardless of which spooler or printer port is in effect.

4121

Printer (-o) To use a print spooler with spooler parameters, use OUTPUT TO PRINTER and specify the spooler parameters with -o. Use one of the following commands:

OUTPUT THROUGH lp spooler-parameters PAGED.

OUTPUT THROUGH lpr spooler-parameters PAGED.

4122

Outer-join Mode (-ojmode)

Outer-join Mode (-ojmode)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value 2 Minimum value 1

-ojmode n

Single-user default 1

Multi-user default 1

An integer specifying the join mode. Use the Outer-join Mode (-ojmode) parameter to specify the mode in which mixed inner and left outer joins, in queries of three or more joined tables, are processed. Mixing inner and left outer joins lets you filter and reduce the amount of data you see on the left side of your left outer joins. When mixing these two types of join, inner joins take precedence over left outer joins. That is, the last inner join in a query causes the results of a prior outer join in the query to be like an inner join. This is because any rows that contain missing data from a prior left outer join are eliminated by the following inner join, if the data from that inner join is also missing. If the subsequent inner join has data, rows containing missing data from the prior left outer join are not eliminated. If you set the value of -ojmode to 1, mixed inner and left outer joins in queries of three or more joined tables are processed as described above. Use this join mode when you want to see rows that contain missing data from a prior left outer join and existent data from a subsequent inner join. This is the default join mode. If you set the value of -ojmode to 2, left outer joins take precedence over inner joins. That is, any rows that contain missing data from a prior left outer join are not eliminated by a subsequent inner join, whether the data from that inner join is missing or not. Use this join mode when you want to see rows that contain missing data from both a prior left outer join and a subsequent inner join. Note: In any query, keeping your inner joins contiguous on the left with any left outer joins contiguous on the right will produce the same result in either join mode.

4123

Password (-P)

Password (-P)
Operating system and syntax Use with CC
password

UNIX Windows Maximum value Minimum value

-P password

Single-user default

Multi-user default

The password of the user connecting to the database. Use Password (-P) together with the User ID (-U) to specify the user password. Progress checks the _User table for the user ID supplied with the -U parameter. When it finds that user ID, it compares the password supplied with the -P parameter with the password in the _User table. If the two passwords match, Progress establishes the database connection. With certain DataServers, the -P and -U parameters pass DataServer login information to the non-OpenEdge database. For information, see your DataServer documentation.

4124

Startup Procedure (-p)

Startup Procedure (-p)

Operating system and syntax Use with CS
filename

UNIX Windows Maximum value Minimum value

-p filename

Single-user default _edit.p

Multi-user default _edit.p

The name of the procedure to run when starting OpenEdge. Use Startup Procedure (-p) to specify a procedure that executes at the start of a OpenEdge session. A common use for the -p parameter is to run a Progress procedure that displays a main application menu. The user can then choose options from the menu to run other Progress procedures. As a built-in security measure, when users press CTRL-C while running a procedure specified by -p, Progress prevents the users from accessing the Procedure Editor by rerunning the specified procedure (unless the application explicitly allows Procedure Editor access). If you use the Batch (-b) startup parameter (MBPRO or BPRO), also use the -p parameter.

4125

Parameter (-param)

Parameter (-param)
Operating system and syntax Use with CS
string

UNIX Windows Maximum value Minimum value

-param string

Single-user default

Multi-user default

A character string that supplies information to a 4GL application. Can also be a comma-separated list of files to open in Procedure Editor buffers. Use Parameter (-param) to specify a character string that can be accessed from 4GL procedures. You can also use this parameter to specify one or more files to load into Procedure Editor buffers. The Procedure Editor only loads the specified files when you use this parameter with a startup command that places you directly in the Procedure Editor. The files are not loaded when you use the parameter with a startup command that places you in the OpenEdge Application Development Environment (ADE) desktop. Within a 4GL procedure, you can access the string by reading the PARAMETER attribute of the system handle.

SESSION

4126

Pending Connection Time (-PendConnTime)

Pending Connection Time (-PendConnTime)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value Minimum value

-PendConnTime n

Single-user default

Multi-user default 0

Time, in seconds, allowed the client to connect to a server. Use Pending Connection Time (-PendConnTime) to prevent connection errors caused by network problems. When a client attempts to connect to an OpenEdge database, the RDBMS assumes that if the client can reach the broker, it can also reach the server. Network problems or incorrect configuration of network devices can prevent the client from reaching the server. In such an instance, the broker, unaware that the clients connection failed, continues to increment its count of connected users. To prevent this problem, OpenEdge brokers use a reservation count on each server and they increment this count whenever they redirect a client to that server. When -PendConnTime is used, the servers examine the timestamp on the latest reservation and, if the Pending Connection Time period has elapsed, the broker assumes that the client has failed to connect. The broker then clears the reservation, making the server available for new clients.

4127

Parameter File (-pf)

Parameter File (-pf)

Operating system and syntax Use with CC, CS, DBS, DS, OID
filename

UNIX Windows Maximum value Minimum value

-pf filename

Single-user default

Multi-user default

The name of a parameter file that contains startup parameters to run OpenEdge. Use Parameter File (-pf) to name a parameter file that includes any number of startup parameters to run OpenEdge. This parameter is especially useful if you regularly use the same parameters to start OpenEdge, or if more parameters are specified than can fit on the command line. This parameter can be included within the parameter file itself to reference another parameter file. Use multiple instances of -pf to name multiple parameter files. This allows you to specify application-specific parameters in one parameter file, database-specific parameters in a second parameter file, and user-specific parameters in yet another file. See Chapter 1, Introduction, for more information about parameter files.

4128

Pin Shared Memory (-pinshm)

Pin Shared Memory (-pinshm)

Operating system and syntax Use With DBS UNIX Windows Maximum value Minimum value

-pinshm

Single-user default

Multi-user default

The Pin Shared Memory (-pinshm) parameter does not have any arguments. Using -pinshm will prevent the database engine from swapping shared memory contents to disk, which can help improve performance.

4129

PROLIB Memory (-plm)

PROLIB Memory (-plm)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-plm

Single-user default

Multi-user default

Use PROLIB Memory (-plm) to allocate a 512byte cache for a standard library directory. Otherwise, when using a standard library, the librarys internal directory is loaded into memory. The directory is used to access the r-code files stored in the library. This parameter slows the librarys speed of access but increases available memory. If you specify -plm with memory-mapped libraries, Progress ignores it. For more information on r-code libraries, see OpenEdge Deployment: Managing 4GL Applications and OpenEdge Development: Progress 4GL Handbook.

4130

PROLIB Swap (-pls)

PROLIB Swap (-pls)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-pls

Single-user default

Multi-user default

Use PROLIB Swap (-pls) to direct Progress to store the r-code files locally in temporary sort files. When accessing r-code files stored in a standard library, Progress generally reads the files directly from the library instead of swapping the files into temporary sort files. However, over a network, direct reads might actually take longer than reading r-code files once and storing them locally in temporary sort files. If you specify -pls with memory-mapped libraries, Progress ignores it. For more information on r-code libraries, see OpenEdge Deployment: Managing 4GL Applications and OpenEdge Development: Progress 4GL Handbook.

4131

Fast Schema Change (-populate)

Fast Schema Change (-populate)

Operating system and syntax Use with CC UNIX Windows Maximum value Minimum value

-populate

Single-user default

Multi-user default

Use Fast Schema Change (-populate) to turn off fast schema change when you are adding fields to a table. Fast schema change is the default behavior. In earlier versions of Progress, adding a field to an existing database table is a time-consuming process for large databases. The DBMS updated the data in each row of the table to reflect the newly added field. Now Progress provides a fast schema change when you are adding fields to a table when all qualifying conditions are met. If all conditions are not met, adding a field causes Progress to update every row in the table.

4132

Configuration Properties File (-properties)

Configuration Properties File (-properties)

Operating system and syntax Use with DBS
filename

UNIX Windows Maximum value Minimum value

-properties filename

Single-user default

Multi-user default

The name of the properties file. Use Configuration Properties File (-properties) to identify the properties file that the AdminServer uses internally to specify startup parameters when starting a database server or servergroup. The default is $DLC/properties/conmgr.properties. You do not use this parameter directly.

4133

Proxy Host (-proxyhost)

Proxy Host (-proxyhost)

Operating system and syntax Use with CC
host-name

UNIX Windows Maximum value

-proxyhost

{ host-name | IP-address }
Single-user default Multi-user default

Minimum value

The name of the host at which the HTTP-based proxy server is located.
IP-address

The IP address of the host at which the HTTP-based proxy server is located. Use the Proxy Host (-proxyhost) parameter to specify the name of the host or the IP address of the host at which the HTTP-based proxy server is located. When binding to a WSDL file via the server objects CONNECT( ) method, all connections made using the HTTP or HTTPS protocol connect to the proxy server at the specified host and port. When you specify this parameter, all connections made by an AppServer client using the HTTP or HTTPS protocol connect to an AppServer Internet Adapter (AIA) instance using the proxy server at the specified host and port. Note: If you specify the Proxy Host (-proxyhost) parameter, you must also specify the Proxy Port (-proxyport) parameter.

4134

Proxy Password (-proxyPassword)

Proxy Password (-proxyPassword)

Operating system and syntax Use with CS
password

UNIX Windows Maximum value

-proxyPassword password

Minimum value

Single-user default

Multi-user default

Password used to authenticate the AppServer client to the HTTP-based Proxy server. password can be a string of up to 512 printable ASCII characters. You should use -proxyPassword when -proxyhost and -proxyport are specified and the Proxy server requires authentication. You can access -proxyPassword using the SESSION:PROXY-PASSWORD attribute. If -proxyhost and -proxyport are not specified on the command line to the 4GL client, any value for -proxyPassword, whether specified with the startup parameter or with the SESSION attribute, is ignored.
password is validated during the AppServer CONNECT() CONNECT()

method. If the password is invalid, the method fails and OpenEdge issues an error message.

If -proxyUserid is not specified or SESSION:PROXY-USERID is not set, the CONNECT() method ignores any value for -proxyPassword.

4135

Proxy Port (-proxyport)

Proxy Port (-proxyport)

Operating system and syntax Use with CC
port-number

UNIX Windows Maximum value 65536

-proxyport

port-number

Minimum value 1

Single-user default

Multi-user default

The port number of the HTTP-based proxy server. Use the Proxy Port (-proxyport) parameter to specify the port on which the HTTP-based Proxy server is listening. When you specify this parameter, all connections made by an AppServer client using the HTTP or HTTPS protocol connect to an AppServer Internet Adapter (AIA) instance using the proxy server at the specified host and port. When binding to a WSDL file via the server objects CONNECT( ) method, all connections made using the HTTP or HTTPS protocol connect to the proxy server at the specified host and port. Note: If you specify the Proxy Port (-proxyport) parameter, you must also specify the Proxy Host (-proxyhost) parameter.

4136

Proxy Userid (-proxyUserid)

Proxy Userid (-proxyUserid)

Operating system and syntax Use with CS
user-id user-id user-id

UNIX Windows Maximum value Minimum value

-proxyUserid user-id

Single-user default

Multi-user default

used to authenticate an AppServer client to the HTTP-based proxy server. The can be a string of up to 512 printable ASCII characters, including the space character.

You can access -proxyUserid using the SESSION:PROXY-USERID attribute. If -proxyhost and -proxyport are not specified on the command-line to the 4GL client, any value for the -proxyUserid, whether specified with the startup parameter or with the SESSION attribute, is ignored. The user-id is validated during the AppServer CONNECT() method. If user-id is invalid, the method fails and OpenEdge issues an error message.

CONNECT()

If -proxyPassword is not specified or SESSION:PROXY-PASSWORD is not set, and -proxyUserid is specified, a blank proxy password is used by the AppServer CONNECT() method.

4137

Quick Request (-q)

Quick Request (-q)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-q

Single-user default

Multi-user default

Use Quick Request (-q) to tell Progress to search PROPATH directories only on the first use of a procedure. Ordinarily in a Progress procedure, when the RUN statement is used to run a subprocedure, Progress searches the directories named by the PROPATH environment variable, looking for a procedure of the same name with a .r extension. If it finds a file with a .r extension (an r-code file), it checks to make sure the r-code file has not changed since that r-code file was created. This search is very useful in a development environment where procedures change regularly and you want to make sure you are always running the most current version of your application. However, in a production environment, you might want to bypass this search. With Quick Request (-q), after the initial search, if the procedure still resides in memory or in the local session-compiled file, Progress uses that version of the procedure rather than searching the directories again. However, Progress always checks whether Data Dictionary definitions related to a procedure were modified. If they were modified, Progress displays an error when it tries to retrieve the procedure.

4138

Non-reliable I/O (-r)

Non-reliable I/O (-r)

Operating system and syntax Use with CC UNIX Windows Maximum value Minimum value

-r

Single-user default Unbuffered I/O

Multi-user default Unbuffered I/O

Use Buffered I/O (-r) to enable buffered I/O to the before-image file. In most cases, avoid using this parameter because it might put database integrity at risk. Caution: If you run Progress with the -r parameter and your system fails because of a system crash or power failure, you cannot recover the database. You must restore the database from a backup and restart processing from the beginning.

Caution: If you are updating a database using buffered I/O and there is a Progress system failure but no hardware failure, Progress can recover the database. In general, you always want complete database integrity or you want fast performance for large tasks, such as loading large amounts of data or doing fiscal year-end processing. The -r parameter does not guarantee complete database integrity, and No Crash Protection (-i) is faster in terms of performance.

4139

Alternate Random Number Generator (-rand)

Alternate Random Number Generator (-rand)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value 2 Minimum value 1

-rand n

Single-user default 1

Multi-user default 1

The type of random number generator. A value of 1 (the default) indicates that Progress should use the original generator; specify a value of 2 to use the alternate. Use Alternate Random Number Generator (-rand) to specify whether to use the original random number generator or the alternate one. The original number generator always generates the same random sequence; that is, the numbers that it generates are random, but each time a session starts, it gives you the same set of numbers from the last session. If you have to generate a different sequence of random numbers, specify the alternate generator. This generator returns a number from a pseudorandom sequence of numbers rather than a truly random sequence.

4140

Reread Nolock (-rereadnolock)

Reread Nolock (-rereadnolock)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-rereadnolock

Single-user default

Multi-user default

Use Reread Nolock (-rereadnolock) to tell Progress that when it attempts to find a record with NO-LOCK, to re-read the record from the database, even if the record is already in a buffer. You can use this parameter to resolve client-server currency conflicts. You can also use it to resolve server-to-server currency conflicts by using it as an AppServer startup parameter via the Progress Explorer or by setting the srvrStartupParam property in the ubroker.properties file for the appropriate AppServer. Keep the following in mind when you use -rereadnolock: It has no affect on records that are retrieved via RECID or ROWID. In that case, Progress will not re-read the record. Instead, it uses the copy of the record already stored in the buffer. If you need the most current version of the record, use the RELEASE statement on all buffers that contain a copy of the record before reading the record, or use the FIND CURRENT or GET CURRENT statement to re-read the record. It has no affect on the behavior of the query cache used for a query with NO-LOCK that is specified via the CACHE phrase of the DEFINE QUERY statement. To force Progress to always re-read the record, set the cache size to zero (0). However, this may significantly degrade performance if the database is accessed across a network. Set the cache size to zero only when it is critical to retrieve the most current version of a record.

4141

Reread Nolock (-rereadnolock) It has no affect on the behavior of the prefetch cache that is used by default when retrieving records NO-LOCK across the network. By default, when executing a CAN-FIND function or a FIND, FOR, or OPEN QUERY statement on a database that is accessed across a network, Progress fetches several records at a time and stores them in a prefetch cache. Progress will only send a request to the database server to fetch more records if the requested record is not in the current prefetch cache. If the record is in the current cache, Progress will not read a new copy of that record even if -rereadnolock is set. To eliminate this cache so that the most current version of the record is always read, use the NO-PREFETCH keyword in the appropriate statements. However, using the NO-PREFETCH keyword may significantly degrade performance. Set NO-PREFETCH only if it is critical to retrieve the most current version of a record.

4142

Run 4GL Client (-rg)

Run 4GL Client (-rg)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-rg

Single-user default

Multi-user default

Use Run 4GL Client (-rg) to indicate that you want to run the 4GL client. Use this parameter if you have more than one type of OpenEdge client and want to limit access/functionally of the session to the 4GL client.

4143

Read-only Media (-RO)

Read-only Media (-RO)

Operating system and syntax Use with CC UNIX Windows Maximum value Minimum value

-RO

Single-user default

Multi-user default

Use Read-only (-RO) to open a database for read-only access. Use -RO to access a database stored on read-only media (a read-only optical disk, for example). Note: Do not run servers for a read-only database. Progress does not support servers for read-only users. If you use the -RO parameter when other users are updating the database, you might see invalid data, such as stale data or index entries pointing to records that have been deleted. A read-only session is essentially a single-user session. Read-only users do not share database resources (database buffers, lock table, index cursors). However, unlike a normal single-user database, a read-only database can be simultaneously accessed by multiple -RO users. When a read-only session starts, it does not check for the existence of a lock file for the database. Furthermore, a read-only user opens the database file, but not the log or before-image files. Therefore, read-only user activity does not appear in the log file. If a database is opened with -RO, the string returned by the DBRESTRICTIONS function includes the keyword READ-ONLY.

4144

Run Query Client (-rq)

Run Query Client (-rq)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-rq

Single-user default

Multi-user default

Use Run Query Client (-rq) to indicate that you want to run the Query client. Use this parameter if you have more than one type of OpenEdge client and want to limit access or functionality of the session to the Query client.

4145

Run Run-time Client (-rr)

Run Run-time Client (-rr)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-rr

Single-user default

Multi-user default

Use Run Run-time Client (-rr) to run the Run-time Client. Use this parameter if you have more than one type of OpenEdge client and want to limit access or functionality of the session to the Run-time Client.

4146

Encrypted Compiler Mode (-rx)

Encrypted Compiler Mode (-rx)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-rx

Single-user default

Multi-user default

Use Encrypted Compiler Mode (-rx) to enable query or run-time OpenEdge clients to compile encrypted source code and access the Data Dictionary to manage schema (for example: for security management and to dump or load .df files). If Progress is started with -rx, you can only compile encrypted source code. Use -rx when you are shipping an application in the form of encrypted source code to end-user sites having query or run-time versions of Progress. You must prepare a tool that end users can run to compile your code, and this tool must include a command that invokes Progress with -rx.

4147

Service Name (-S)

Service Name (-S)

Operating system and syntax Use with CC, DBS
service-name

UNIX Windows Maximum value

-S

{ service-name | port-number }
Single-user default Multi-user default

Minimum value

The name of the service to be used by the broker process.

port-number

The port number of the host; if using Progress Explorer, the port number of the NameServer. Use Service Name (-S) to specify the service or port number to be used when connecting to a broker process or used by a broker process on the host machine. You must use this parameter when you are starting: A broker or server on a machine that will serve remote users. Multi-user Progress as a remote user.

The system administrator must make an entry in the services file that specifies the server or broker name and port number. When the broker spawns a server, the server inherits all of the network parameters (except the Service Name parameter) from the broker. Because there is no restriction on the number of brokers you can start, you can have multiple brokers running with different network parameters. See also the Server Group (-servergroup) startup parameter description.

4148

Service Name (-S) Table 43 shows how the broker, server, and remote client interpret each of their parameters when you use the -S parameter. Table 43: Module Broker Server Remote Client Parameter interpretation with Service Name (-S) Interpretation Parameters apply to the connections on which the broker is listening for connection requests from remote clients. Parameters apply to the connection between the server and the remote client. Parameters identify the connection parameters to the broker or the server.

To run multi-user Progress from a remote network node, use both the Host Name (-H) and Service Name (-S) parameters.

4149

Stack Size (-s)

Stack Size (-s)

Operating system and syntax Use with CS
1

UNIX Windows Maximum value 5,242,8781 Minimum value 9

-s n

Single-user default 40

Multi-user default 40

Actual maximum value is limited only by available memory.

The size of the stack in 1KB units. Use Stack Size (-s) to change the size of the stack (an internal memory area used by Progress program modules). Note: It is recommended that the -s session startup parameter be set to 128. Setting this startup parameter to a smaller value may result in runtime errors in some environments. Increase the stack size if one of the following messages appears:

SYSTEM ERROR: stkpush: stack overflow. Increase -s parameter. SYSTEM ERROR: stkditem: stack overflow. Increase -s parameter.

Stack overflow errors are most likely when data definitions are loaded for very large tables or use recursive procedures. Note: If your application passes array parameters to procedures or functions, your stack size requirements can increase significantly.

4150

Semaphore Sets (-semsets)

Semaphore Sets (-semsets)

Operating system and syntax Use with DBS

UNIX Maximum value Maximum Number of Users +1 Minimum value 1

-semsets n

Single-user default

Multi-user default 1

An integer specifying the number of semaphore sets available to the OpenEdge broker. Use Semaphore Sets (-semsets) to change the number of semaphore sets available to the OpenEdge broker. When more than 1,000 users connect to a single database, there might be high contention for the semaphore set. If there is a lot of semaphore contention on a system, using multiple semaphore sets helps alleviate this contention and improve performance on high user counts. For more information on using semaphore sets, see OpenEdge Data Management: Database Administration.

4151

Server Group (-servergroup)

Server Group (-servergroup)

Operating system and syntax Use with DBS
name

UNIX Windows Maximum value Minimum value

-servergroup name

Single-user default

Multi-user default

Specifies the name of the logical collection of server processes. Use Server Group (-servergroup) to identify the logical collection of server processes to start. The name you specify must match the name of a servergroup in the conmgr.properties file. Use the Progress Explorer tool to create servergroups and save them in the conmgr.properties file. Do not edit the conmgr.properties file directly. To start a database configuration use Progress Explorer or the DBMAN utility.

4152

Type of Server to Start (-ServerType)

Type of Server to Start (-ServerType)

Operating system and syntax Use with DBS
4GL

UNIX Windows Maximum value

-ServerType

[4GL|SQL|Both]
Multi-user default Both

Minimum value

Single-user default Both

Indicates the broker supports only 4GL servers.

SQL

Indicates the broker supports only SQL servers.

Both

Indicates the broker supports both 4GL and SQL servers. Use the Type of Server to Start (-ServerType) parameter to limit the type of server the broker can start. To change the value of -ServerType, use the config.properites file or the command line.

4153

Session Timeout (-sessiontimeout)

Session Timeout (-sessiontimeout)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value Minimum value

-sessiontimeout n

Single-user default

Multi-user default 180

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.

4154

AS/400 Server Program Name (-Sn)

AS/400 Server Program Name (-Sn)

Operating system and syntax Use with CC UNIX Windows (SNA Only) Maximum value Minimum value
-Sn

Single-user default

Multi-user default

Use Server Program Name (-Sn) with SNA to specify that the Server program start on the AS/400 with a Progress connection request.

4155

Spin Lock Retries (-spin)

Spin Lock Retries (-spin)

Operating system and syntax Use with DBS
1

UNIX Windows Maximum value Minimum value 0

-spin n

Single-user default 0

Multi-user default 0, 60001

Single processor machine the default is 0. Multi-processor machine 6000.

The number of times a process tries to acquire a latch before pausing. Use Spin Lock Retries (-spin) to set a value to use the spin lock mechanism or a system of semaphores and queues. If the value of n is greater than 0, then a spin lock algorithm is used for shared-memory data structures. When a process has to lock a shared-memory structure, the process tries up to n times to acquire the latch for that structure. If it has not acquired the latch in n tries, the process pauses, or naps. The length of the pause increases gradually if the process repeatedly fails to acquire a latch. After the allotted nap time, the process wakes up and tries to acquire the lock again. If it fails to acquire the lock, it will retry up to the number of tries specified by n. If the value of n is 0, a system of semaphores and queues is used instead of spin locks. The spin lock algorithm is much more efficient than using semaphores when you have multiple processors. In some cases, if the value of n is 1, it might improve performance even on a single-processor machine because Progress uses the spin lock mechanism. Do not set this parameter to a value larger than 1 if your machine has only one processor. On multi-processor machines, try a value of 5000 * # of CPUs. If this causes too much CPU usage, reduce the value. If you have fast processors, a value as high as 10,000 * # of CPUs might be effective.

4156

Spin Lock Retries (-spin) You can evaluate the -spin values through the OpenEdge Monitor (PROMON utility) R&D options. See OpenEdge Data Management: Database Administration for more information on the PROMON utility. The -spin parameter controls the performance indicator called resource waits. By setting the -spin value higher, you can reduce the resource waits. Note that when setting the -spin value higher ceases to reduce the resource waits, continuing to set it higher can adversely effect CPU utilization. To view the resource waits value: Access PROMON and enter R&D at the main menu. Choose option 3. Other Displays, then choose option 1. Performance Indicators to view the resource waits. Resource waits is the last item reported in the listing.

4157

SQL Open Cursors (-SQLCursors)

SQL Open Cursors (-SQLCursors)

Operating system and syntax Use with DBS
value

UNIX Windows Maximum value 512 Minimum value 10

-SQLCursors value

Single-user default

Multi-user default 50

Number of cursors open at one time. Use SQL Open Cursors (-SQLCursors) to define the maximum number of cursors open at any one time.

4158

SQL Stack Size (-SQLStack)

SQL Stack Size (-SQLStack)

Operating system and syntax Use with DBS UNIX Windows Maximum value System Dependent Minimum value 1

-SQLStack n

Single-user default 1

Multi-user default 1

The size of the stack in 1MB units. Use SQL Stack Size (-SQLStack) to change the size of the SQL stack (an internal memory area used by SQL program modules). Use the command line to change the value of -SQLStack.

4159

SQL Statement Cache Size (-SQLStmtCache)

SQL Statement Cache Size (-SQLStmtCache)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value Minimum value

-SQLStmtCache n

Single-user default

Multi-user default 100

The number of statements to be stored in the SQL Statement Cache. Use SQL Statement Cache Size (-SQLStmtCache) to set the number of statements that can be stored in the SQL cache. Use the command line to change the value of -SQLStmtCache.

4160

SQL Sorting Memory (-SQLTempBuff)

SQL Sorting Memory (-SQLTempBuff)

Operating system and syntax Use with DBS
value

UNIX Windows Maximum value 200000 Minimum value 100

-SQLTempBuff value Single-user default 1000 Multi-user default 1000

Size in K-bytes of the temporary table buffers in main memory cache. Increasing the value of -SQLTempBuff lessens the amount of IO for temporary tables. Decreasing the value frees memory for other uses. Note: Each connection allocates one temporary table buffer. Use SQL Sorting Memory (-SQLTempBuff) to define the size in K-bytes of the temporary table buffers in main memory cache.

4161

SQL Sorting on Disk (-SQLTempDisk)

SQL Sorting on Disk (-SQLTempDisk)

Operating system and syntax Use with DBS
value

UNIX Windows Maximum value 100000000 Minimum value 5000

-SQLTempDisk value Single-user default 500000 Multi-user default 500000

Size in K-bytes of the temporary table for backup storage on disk. Increasing the value of -SQLTempDisk benefits the sorting of very large amounts of data. Note: Since disk space is allocated on demand, this parameter is an upper bound. Use SQL Sorting on Disk (-SQLTempDisk) to define the size in K-bytes of the temporary table for backup storage on disk.

4162

SQL Temp Table Data Page (-SQLTempPgSize)

SQL Temp Table Data Page (-SQLTempPgSize)

Operating system and syntax Use with DBS
value

UNIX Windows Maximum value 256

-SQLTempPgSize value Minimum value 4 Single-user default 8 Multi-user default 8

Size in K-bytes of the temporary table data page. Increasing the value of -SQLTempPgSize aids sorting data with a large number of values per row. Use SQL Temp Table Data Page (-SQLTempPgSize) to define the size in K-bytes of the temporary table data page, which is the upper limit of temporary table record size.

4163

SSL-based Connection (-ssl)

SSL-based Connection (-ssl)

Operating system and syntax Use with CC,DBS UNIX Windows Maximum value Minimum value

-ssl

Single-user default

Multi-user default

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/IP connection. Note: Be sure you need SSL before using this parameter. SSL incurs more or less heavy performance penalties, depending on resources and load. For more information, see OpenEdge Getting Started: Security.

4164

Stash Area (-stsh)

Stash Area (-stsh)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value 31 Minimum value 1

-stsh n

Single-user default 2

Multi-user default 2

The number of 1KB blocks for the stash area. Use Stash Area (-stsh) to specify the number of 1KB blocks to allocate to the stash area, which Progress uses as temporary storage for modified index fields. The default size is sufficient for most index fields, but large character fields with a word index might require more space. You can calculate an appropriate stash size by taking the size in bytes of the largest field with a word index, doubling that value, and adding 1KB. For example, if the largest word indexed field is 2,000 characters long, set -stsh to 5 to create a stash area of 5KB. If you do not allocate enough space, Progress terminates with a fatal error. If this occurs, restart Progress with a larger stash area.

4165

Temporary Directory (-T)

Temporary Directory (-T)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-T dirname

Single-user default Working directory

Multi-user default Working directory

dirname

The directory in which to create temporary files. Use Temporary Directory (-T) to specify a directory for temporary files. If you do not use this parameter, Progress puts these temporary files in the current working directory. On UNIX and Windows, these filenames begin with a prefix of lbi, dbi, pge, srt, or trp, and end with the process ID of the users OpenEdge session. Note: Access the -T parameter using the SESSION:TEMP-DIR attribute. This attribute is read-only. The following table shows descriptions of these prefixes:

Temp file LBI DBI PGE SRT TRP

Usage Local before-image (subtransaction undo) Store temporary tables Edit buffer contents Temporary sort space; session compile storage Store Data Dictionary changes until they are saved

4166

Temporary Directory (-T) On UNIX, Progress names these files uniquely for each user to avoid filename conflicts. Furthermore, Progress stores these files as unlinked with no visible name in the UNIX file system (unless you use Save Temp Files (-t). On Windows, if two or more users share the same working directory and there is a conflict of temporary files, the following message appears:

Unable to open or create filename, error 3

4167

Save Temp Files (-t)

Save Temp Files (-t)

Operating system and syntax Use with CS

UNIX Maximum value Minimum value

-t

Single-user default

Multi-user default

Use Save Temp Files (-t) to make temporary files visible on UNIX. Typically, temporary files (LBInumber, SRTnumber, PGEnumber, DBInumber, and TRPnumber) are invisible (unlinked on UNIX) when Progress is running. In these filenames, number is the process ID of the users OpenEdge session. The -t parameter also makes the entries visible after Progress aborts. However, if Progress aborts, delete the temporary files yourself. With or without the -t parameter, Progress always deletes the temporary files when it terminates normally.

4168

Table Range Size (-tablerangesize)

Table Range Size (-tablerangesize)

Operating system and syntax Use with DBS
n

UNIX Windows Maximum value Minimum value

-tablerangesize n

Single-user default

Multi-user default

The number of tables for which you want to track access statistics. Use Table Range Size (-tablerangesize) to specify the number of tables for which you want to collect statistics. For more information on tracking table statistics, see OpenEdge Data Management: Database Administration.

4169

Speed Sort (-TB)

Speed Sort (-TB)

Operating system and syntax Use with CS
blocksize

UNIX Windows Maximum value 31 Minimum value 1

-TB blocksize

Single-user default 2

Multi-user default 2

The block size in kilobytes, to allocate when sorting records for reports and when rebuilding indexes. The default block size is 2K but can be reset anywhere from 1KB to 31KB. Use Speed Sort (-TB) primarily to improve sort performance, particularly during index rebuild operations. If you increase the block size beyond 2KB, Progress sorts records faster but uses more memory and disk space in the process. If system memory is severely limited, you might actually choose to lower the block size. Sort space is allocated in the SRT file, a temporary session file having a system-generated unique name with the prefix srt. Progress uses the SRT file to store session-compile modules and as temporary work space during sorting (including rebuilding indexes). Use -TB to set the SRT file block size-the increments by which the SRT file grows. In summary, increase -TB to at least 8 to improve index rebuild operations by 15 percent or more. Or, decrease -TB to 1 to relieve severe Windows memory shortages during sort operations. See also the description of the Merge Number (-TM) startup parameter. Note: Increasing the -TB value to 4 or more can improve network performance when Progress reads large r-code files across a network.

4170

Merge Number (-TM)

Merge Number (-TM)

Operating system and syntax Use with CS
n

UNIX Windows Maximum value 32 Minimum value 1

-TM n

Single-user default 5

Multi-user default 5

The number of blocks or streams to be simultaneously merged during the sort process. Use Merge Number (-TM) to increase the speed of the merge phase of the sort process (at the cost of increased temporary memory usage). See also the description of the Speed Sort (-TB) startup parameter.

4171

Token (-tok)

Token (-tok)
Operating system and syntax Use with CS UNIX Windows Maximum value System dependent1 Minimum value 1

-tok n

Single-user default 1024

Multi-user default 1024

Limited by available memory.

The number of tokens allowed in a 4GL statement. Use Token (-tok) to specify the maximum number of tokens allowed in a single 4GL statement (default 1,024 tokens). If you exceed the default number, Progress prompts you to use this startup parameter to increase the number of tokens allowed.

4172

Trigger Location (-trig)

Trigger Location (-trig)

Operating system and syntax Use with CC
dir-name, lib-name

UNIX Windows Maximum value

-trig

{ dir-name | lib-name }
Single-user default Multi-user default

Minimum value

The location of the database 4GL triggers. Use Trigger Location (-trig) to identify the name of the directory or library that contains the database 4GL triggers for a database. Library names must have a .pl extension. Progress interprets all other extensions as directory names. If you do not use Trigger Location (-trig) when connecting to the database, Progress searches the PROPATH for the triggers. For more information about database triggers, see OpenEdge Development: Progress 4GL Handbook. Note: If you are generating the local binary schema cache, do not connect to the database using Trigger Location (-trig) and the Schema Cache File (-cache) together.

4173

User ID (-U)

User ID (-U)
Operating system and syntax Use with CC
userid

UNIX Windows Maximum value Minimum value

-U userid

Single-user default

Multi-user default

The user ID of the user. Use User ID (-U) with Password (-P) to specify the user ID. Progress checks the _User table for the user ID supplied with the -U parameter. When it finds that user ID, it compares the password (after it has encoded the password) supplied with the -P parameter with the password in the _User table. If the two passwords match, Progress assigns the user ID to the OpenEdge session. Otherwise, the user is not allowed to connect to the database. With certain DataServers, the -U and -P parameters pass DataServer login information to a non-OpenEdge database. For more information, see your DataServer documentation.

4174

Use OS Locale (-useOsLocale)

Use OS Locale (-useOsLocale)

Operating system and syntax Use with CS

Windows Maximum value Minimum value

-useOsLocale

Single-user default

Multi-user default

The Use OS Locale (-useOsLocale) parameter sets certain default localization options in OpenEdge clients. It causes Progress to set the SESSION system handle attributes based on the current Windows locale settings, shown in Table 44. The table also shows the startup parameters that individually affect the value of each attribute. Table 44: Attributes set by Use OS Locale (useOsLocale) Associated startup parameters Date Format (-d) Fractional Separator (-numdec) European Numeric Format (-E) Fractional Separator (-numdec) Thousands Separator (-numsep)
NUMERIC-SEPARATOR

SESSION system handle attribute

DATE-FORMAT NUMERIC-DECIMAL-POINT NUMERIC-FORMAT

Thousands Separator (-numsep)

If any of the startup parameters shown in the table appear on the same command line with the parameter, any that follow -useOsLocale override the setting from -useOsLocale and any that -useOsLocale follows are overridden by the setting from -useOsLocale.
-useOsLocale

For more information on these SESSION system handle attributes, see OpenEdge Development: Progress 4GL Reference.

4175

Version 6 Colon (-v6colon)

Version 6 Colon (-v6colon)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-v6colon

Single-user default

Multi-user default

Use Version 6 Colon (-v6colon) to direct Progress to perform colon alignment for unlabeled fields, as in Version 6. If you do not specify this parameter, Progress moves the field two characters to the right.

4176

Version 6 Query (-v6q)

Version 6 Query (-v6q)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-v6q

Single-user default

Multi-user default

Use Version 6 Query (-v6q) to direct the OpenEdge server to use only a single index when resolving FOR EACH statements. If you do not use this parameter, the server might use more than one index. Using more than one index is more efficient, but might change the order in which records are returned. The -v6q parameter also causes cursor repositioning with FOR EACH statements, as in Version 6.

4177

Windows Passthrough Printing (-Wa -wpp)

Windows Passthrough Printing (-Wa -wpp)

Operating system and syntax Use with CS

Windows Maximum value Minimum value

-Wa -wpp

Single-user default

Multi-user default

Use Windows Passthrough Printing (-Wa -wpp) to enable WPP mode for the session. You can only use this startup parameter at the command line. It is ignored when used in a .pf file. It must be the last parameter in the command.

4178

Windows Single Session (-wss)

Windows Single Session (-wss)

Operating system and syntax Use with CS

Windows Maximum value Minimum value

-wss

Single-user default

Multi-user default

Use Windows Single Session (-wss) to limit a user to running only one OpenEdge client session at a time. This parameter applies only to a Windows GUI client. If an existing OpenEdge session is running on the machine when -wss is specified, the new session terminates and the windows of the existing session are brought forward to alert the user. To avoid unnecessary processing of other parameters, use the -wss parameter first on the command line. If more than one OpenEdge application is installed on a users machine, do not use the -wss parameter else it will prevent a user from running two or more applications at the same time. In addition, the -wss parameter does not recognize versions of Progress prior to Version 9.0.

4179

Windows Exit - No Dialog (-wy)

Windows Exit - No Dialog (-wy)

Operating system and syntax Use with CS

Windows Maximum value Minimum value

-wy

Single-user default

Multi-user default

Use Windows Exit - No dialog (-wy) to prevent Progress from prompting you for confirmation when Windows is shut down with Progress active.

4180

Statistics (-y)

Statistics (-y)
Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-y

Single-user default

Multi-user default

Use Statistics (-y) to collect procedure access and usage statistics throughout the OpenEdge session. At session end, Progress writes these statistics to the default output file client.mon. For detailed information on the output written to the client.mon file, see OpenEdge Data Management: Database Administration. At startup, the -y parameter sends a report of all the startup parameters to the output file. This report includes all default values, overridden values, and values you set at startup. Unlike the other statistics that the -y parameter collects, this report is not written at session end and is not affected by the SHOW-STATS statement. Note: The specific statistics displayed might change periodically as new Progress features are implemented. The edit buffer map statistics are written each time a user exits from Progress or uses the SHOW-STATS statement. These lines list the procedures currently in the edit (or execution) buffer and their r-code sizes. Note: If you cannot execute SHOW-STATS from the Procedure Editor or cannot add the statement to your Progress code (for example, if while using Run-time Progress), you can specify Statistics with CTRL-C (-yc) instead of the -y parameter. Both parameters behave the same way, except -yc lets you use CTRL-C as a substitute for the SHOW-STATS statement. The program-access statistics are written to the output file when the session ends or when you use the SHOW-STATS statement. In the output, temp file reads and writes are reads and writes to the SRT file, which stores each users session compiles and active r-code files. The Bytes column is a cumulative total. The Stat file checks are recorded because they represent a relatively time-consuming system call. Unless you invoke Quick Request (-q), Progress makes a stat call each time a precompiled subprocedure is called with the RUN statement. 4181

Statistics (-y) Progress places the default output file (client.mon) in the current working directory.; however, you can specify a different output file by using the CLIENTMON environment variable. Simply set CLIENTMON to point to the file you want to use. For example, in a UNIX environment, if you wanted to use a file named stats in the /usr/tmp directory, enter the following command at the system prompt:

CLIENTMON=/usr/tmp/stats; export CLIENTMON

4182

Statistics with CTRL-C (-yc)

Statistics with CTRL-C (-yc)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-yc

Single-user default

Multi-user default

Use Statistics with CTRL-C (-yc) to allow you to press CTRL-C as a substitute for executing the SHOW-STATS statement. Use this parameter if you cannot execute SHOW-STATS from the Procedure Editor or cannot add the statement to your Progress code (for example, if while using run-time Progress). When you specify this parameter, it disables CTRL-C as an interrupt signal. In addition, pressing only emulates SHOW-STATS without the CLEAR option.

CTRL-C

4183

Segment Statistics (-yd)

Segment Statistics (-yd)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-yd

Single-user default

Multi-user default

Use Segment Statistics (-yd) to write segment statistics to the client monitor file (client.mon, by default). This provides: A breakdown of an r-code file by segment type, including the number of segments and their total size. Read and write access to the sort file by segment type and access type, including the number of times the sort file was accessed and the number of bytes read from/written to the sort file.

4184

Four Digit Year Default (-yr4def)

Four Digit Year Default (-yr4def)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-yr4def

Single-user default

Multi-user default

Use Four Digit Year Default (-yr4def) to output a four-digit year from the EXPORT, MESSAGE and PUT UNFORMATTED statements that may use a two-digit year. This option causes all dates to use a four-digit year, regardless of what is specified by the Century year Offset (-yy) startup parameter. If you do not use this parameter, the EXPORT, MESSAGE and PUT UNFORMATTED statements produce a two-digit year for the date if it is within the 100 year period defined by the Century Year Offset (-yy) startup parameter. If the date is outside of that 100 year period, these statements produce a four-digit year for the date. Using -yr4def does not affect statements such as DISPLAY, UPDATE and PUT (without UNFORMATTED), nor any default schema or program variable date formats, which continue to use the default format 99/99/99. These statements have the FORMAT phrase where an overriding date format can be given, if the 4-digit year is desired, or the fields and variables can be defined with the explicit 99/99/9999.

4185

Statistics With Cross-reference (-yx)

Statistics With Cross-reference (-yx)

Operating system and syntax Use with CS UNIX Windows Maximum value Minimum value

-yx

Single-user default

Multi-user default

Use Statistics with Cross-reference (-yx) to collect procedure call statistics and write them to an output file. With this parameter, you can monitor information to answer the questions: How many calls were made in a given period of time? How long did a procedure spend executing? How often was a procedure swapped to and from the temporary file (SRT file)?

Progress places the default output file for the -yx parameter, proc.mon, in your current working directory. However, you can specify a different output file by using the PROCMON environment variable. Simply set PROCMON to point to the file you want to use. For example, in a UNIX environment, if you want to use a file named stats in the /usr/tmp directory, enter the following command on the command line:

PROCMON=/usr/tmp/stats; export PROCMON

Use the SHOW-STATS statement to write the procedure call statistics to the output file. The CLEAR option sets all counters and timers (such as Calls and Time) to 0. When you exit Progress, the -yx parameter writes the procedure call statistics to the output file whether or not you use SHOW-STATS.

4186

Statistics With Cross-reference (-yx) The following example shows sample procedure call statistics as they appear in the output file:

Wed Feb 6 16:19:05 2002 Procedure call statistics: Caller <top> _edit _edit _prostar _edit _edit _proedit _proedit _proedit _proedit _proedit Callee _edit _adeload _prostar _login _setcurs _proedit _toollic _tmpfile _kvlist _setcurs _adehelp 16:19:21 Calls 1 1 1 1 2 1 1 2 2 4 1 Rd Bytes 3789 9542 6931 5087 562 181029 2570 1510 2624 0 3279 Reread 0 0 0 0 0 0 0 0 0 0 0 Time 16 10 23 73 20 12180 268 140 26 63 97

Load Size 3789 9542 6931 5087 562 181029 2570 1510 2624 562 3279

The fields that appear in the output file proc.mon are as follows: Caller The names of any calling procedures. The word <top> indicates there was no calling procedure, and you ran the called procedure directly from the Procedure Editor. Callee The names of the called procedures. Load Size The size, in bytes, of each called procedure as Progress loads it into memory. If you see a load size of 0, the called procedure is an uncompiled source procedure (.p file), or an r-code file (.r file) that was previously loaded into memory. Calls The number of times the Caller procedure calls the Callee procedure. Rd Bytes Generally, the called procedures load size. However, if the procedure is swapped out of memory and later restored, Rd bytes equals the procedures Load Size added to the number of bytes read from the SRT file. Rd Bytes grows larger each time the procedure is swapped out of memory and restored from the SRT file. Reread The number of bytes Progress reads from the SRT file to restore a Caller procedure that was overwritten. Progress restores only what is necessary to continue executing the Caller procedure. In some cases, this is less than the amount swapped to the SRT file. Time The total execution time of the called procedure, in milliseconds.

4187

Century Year Offset (-yy)

Century Year Offset (-yy)

Operating system and syntax Use with CS, DBS
n

UNIX Windows Maximum value Minimum value

-yy n

Single-user default 1950

Multi-user default 1950

A four-digit year (1990, for example). The default is 1950. Use Century Year Offset (-yy) to determine the start of the 100-year period in which a date with a two-digit year is valid. Some OpenEdge applications reserve only two-digits for the year in the date format. When, for example, -yy is set at 1950, Progress determines if the two-digit year value is greater or less than 50. If the year is greater than 50, Progress assumes that the date is in the twentieth century. If the year is less than 50, Progress assumes that the date is in the twenty-first century. Table 45 shows examples of -yy. Table 45: -yy 1900 Century setting and date format Year (as supplied in DATE format) 50-99 00-49 1950 50-99 00-49 1980 80-99 00-79 Result of year function 1950-1999 1900-1949 1950-1999 2000-2049 1980-1999 2000-2079

Notice that all two-digit year values expand into the 100-year period beginning with -yy.

4188

Century Year Offset (-yy) To test the effect of -yy, start Progress with a different -yy value and run the following procedure:

DEFINE VARIABLE ddate AS DATE. DISPLAY "Enter date or Press F4 to end." WITH FRAME msg. REPEAT: SET ddate LABEL "Date" WITH SIDE-LABELS. DISPLAY YEAR(ddate) FORMAT "9999" LABEL "=> Year" WITH SIDE-LABELS. END.

If you use a hard-coded date containing a two-digit year in a .p file, Progress honors the -yy parameter and expands the two-digit year to a four-digit year during compilation. However, this may not match the runtime -yy. For this reason, Progress Software recommends that you use four digit years for hard-coded dates in programs. For example:

DEFINE VARIABLE hdate AS DATE INITIAL 01/01/2001.

Note: When you dump or load any database, the -yy setting you load with must match the -yy setting that was used for dumping, unless you use the Four Digit Year Default (-yr4def) startup parameter for dumping. This startup parameter provides the same functionality as the SESSION:YEAR-OFFSET attribute.

4189

Century Year Offset (-yy)

4190

Index

Numbers
-1 startup parameter 42 4GL parameters client 35

After-image Stall (-aistall) startup parameter 46 After-image writer PROAIW utility 211 stopping 211 -aibufs startup parameter 45

A
ADE Desktop startup commands Windows 24 ADE r-code location (-baseADE) startup parameter 410 -admingroup startup parameter 43 -adminport startup parameter 44 AdminServer Group (-admingroup) startup parameter 43 AdminServer Port (-adminport) startup parameter 44 After-image buffers 211 After-Image Buffers (-aibufs) startup parameter 45

-aistall startup parameter 46 AIW, see also After-image writer Alternate Random Number Generator (-rand) startup parameter 4140 APW, see also Asynchronous page writer AS/400 Host Name (-H) startup parameter 463 AS/400 Ignore Stamp (-is) startup parameter 473 AS/400 Server Program Name (-Sn) startup parameter 4155 Async Queue Size (-asyncqueuesize) startup parameter 47 Asynchronous page writer 212 stopping 212

OpenEdge Deployment: Startup Command and Parameter Reference -asyncqueuesize startup parameter 47 Auto Server (-m1) startup parameter 491 Auto Server server type 491 -bistall startup parameter 416 -bithold startup parameter 417 BIW, see also Before-image writer Bleeding Record Lock (-brl) startup parameter 420 Block sizes sorting 4170 Blocks in Database Buffers (-B) startup parameter 48 -bn startup parameter 219 -Bp startup parameter 418 -Bpmax startup parameter 419 BPRO command 26 -brl startup parameter 420 Brokers shutting down permissions 221 -Bt startup parameter 421 Buffer Size for Temporary Tables (-Bt) startup parameter 421 Buffered I/O (-r) startup parameter 4139 Buffers after-image specifying 45 before-image specifying 415 blocks in database buffers 48 changing size of local record 479 edit 4181 local 4105 message 499 private read-only 418 server startup parameters 315 -by startup parameter 218

B
-B startup parameter 48 -b startup parameter 49 PROSHUT command 218 Base Index (-baseindex) startup parameter 412 -baseADE startup parameter 410 Basekey (-basekey) startup parameter 413 Base Table (-basetable) startup parameter 414 Batch (-b) startup parameter 49 Batch startup commands BPRO 26 MBPRO 28 single-user 23 Windows 24 Before-Image Buffers (-bibufs) startup parameter 415 Before-Image Cluster Age (-G) startup parameter 461 Before-imaging 415 Before-Image Buffers (-bibufs) startup parameter 213 Before-image writer 213 starting 415 stopping 213 Before-imaging -Mf startup parameter 496 -bibufs startup parameter 213, 415

Index2

Index

C
-C disconnect specified user PROSHUT Command 219 -C list users PROSHUT command 219 -c startup parameter 422 -cache startup parameter 423 Case Table (-cpcase) startup parameter 432 Century (-yy) startup parameter 4188 Check Double-byte Enabled (-checkdbe) startup parameter 425 Check Width (-checkwidth) startup parameter 426 -checkdbe startup parameter 425 -checkwidth startup parameter 426 Client Connection startup parameters 312 Client Internationalization startup parameters 38 Client Logging (-clientlog) startup parameter 428 Client Performance startup parameters 33 Client Session startup parameters 32 4GL 35 performance 33 product-type 34 Client startup parameters database connection 312 session statistics 310 windows session 311 -clientlog startup parameter 428 Clients defined 12

Code page establishing case rules 432 for printer output 436 for reading r-code text segments 437 for writing r-code text segments 438 identifying 434 identifying collation table 433 used to write log messages 435 Collation Table (-cpcoll) startup parameter 433 Colon alignment -v6colon startup parameter 4176 Commas Progress interpretation 454 Communications Parameter File (-cp) startup parameter 431 Compiling encrypted source code 4147 Configuration Properties File (-properties) startup parameter 4133 Connecting over a wide area network 423 to non-OpenEdge databases 453 Conversion Map (-convmap) startup parameter 427, 430 -convmap startup parameter 427, 430 -cp startup parameter 431 -cpcase startup parameter 432 -cpcoll startup parameter 433 -cpinternal startup parameter 434 -cplog startup parameter 435 -cpprint startup parameter 436 -cprcodein startup parameter 437 -cprcodeout startup parameter 438

Index3

OpenEdge Deployment: Startup Command and Parameter Reference -cpstream startup parameter 439 -cpterm startup parameter 440 -cs startup parameter 441 CTRL-C statistics 4183 Cursor Size (-cs) startup parameter 441 ORACLE index hints 4113 specifying keywords 452 starting a broker 214 startup parameters 322 using Server Join (-nojoinbysqldb) 4114 DataService (-DataService) startup parameter 444 -DataService startup parameter 444

D
-D startup parameter 442 -d startup parameter 443 Data bulk loading 467 Database connecting to 445 over a wide area network 423 Database connection client startup parameters 312 Database integrity 467 Database names logical 480 physical 445 Database quiet points 215 Database Server parameters 315 Database shutdown avoiding 46, 416, 417 Database Type (-dt) startup parameter 453 DataServer (-Dsrv) startup parameter 452 DataServer startup parameters 322 DataServers connecting through a NameServer 444 Join by SQLDB 4114 ODBC 444, 452, 4117 ORACLE 444, 452, 4114, 4117

Date format (-d) startup parameter 443 -db startup parameter 312, 445 Debug Alert (-debugalert) startup parameter 447 -debug startup parameter 446 -debugalert startup parameter 447 Debugger (-debug) startup parameter 446 -debugReady startup parameter 449 Decimals Progress interpretation 454 Delayed BI File Write (-Mf) startup parameter 496 -dictexps startup parameter 450 Dictionary Expressions (-dictexps) startup parameter 450 Direct I/O (-directio) startup parameter 451 -directio startup parameter 451 Directories for temporary files 4166 Directory entries compiled procedures 442 Directory Size (-D) startup parameter 442 Disconnect specified user PROSHUT command 219

Index4

Index Double-byte characters check 425 -Dsrv startup parameter 452 -dt startup parameter 453 Dynamics Parameter (-icfparam) startup parameter 469 -fc startup parameter 458 File descriptors 494 Files client.mon 4181 keyword 475 parameters 13 saving temporary 4168 searching 4138 startup.pf 13 Filtering Asynchronous COM Events (-filterocxevents) startup parameter 459 -filterocxevents startup parameter 459 Force Access (-F) startup parameter 457 PROSHUT command 219 Four Digit Year Default (-yr4def) startup parameter 4185 Four-digit year 4188 Fractional Separator (-numdec) startup parameter 4118 Free space consolidation of 4105

E
-E startup parameter 454 Edit buffers 4181 Editing parameter files 15 Enable Attachable Debugging (-debugReady) startup parameter 449 Encrypted Compiler Mode (-rx) startup parameter 4147 Encrypted source code 4147 Error messages 468 European Numeric Format (-E) startup parameter 454 Event-Level (-evtlevel) startup parameter 455 -evtlevel startup parameter 455 Expand Browse (-expandbrow) startup parameter 456 -expandbrow startup parameter 456

G
-G startup parameter 461 Group Delay (-groupdelay) startup parameter 462 -groupdelay startup parameter 462 -Gw startup parameter 219

F
-F startup parameter 457 PROSHUT command 219 Fast Schema Change (-populate) startup parameter 4132

H
-H startup parameter 219, 463 -h startup parameter 464

Index5

OpenEdge Deployment: Startup Command and Parameter Reference Hardlimit (-hardlimit) startup parameter 465 -hardlimit startup parameter 465 -hash startup parameter 466 Hash Table Entries (-hash) startup parameter 466 Help button adding to alert boxes 447 Host Name (-H) startup parameter 463 PROSHUT command 219 Internal Code Page (-cpinternal) startup parameter 434 -is startup parameter 473 -isnoconv startup parameter 474

J
Java classpath identifying 427

K
-k startup parameter 475 Key Alias (-keyalias) startup parameter 476 Key Alias Password (-keyaliaspasswd) startup parameter 477 -keyalias startup parameter 476 -keyaliaspasswd startup parameter 477 Keyword Forget List (-k) startup parameter 475 Kill users (-by) startup parameter PROSHUT command 218

I
-i startup parameter 467 -icfparam Dynamics startup parameter 469 Index Base (-baseindex) startup parameter 412 Index Cursors (-c) startup parameter 422 Index Hint (-noindexhint) startup parameter 4113 Index Range Size (-indexrangesize) startup parameter 470 -indexrangesize startup parameter 470 -ininame startup parameter 471 Initial Value Segment No Convert (-isnoconv) startup parameter 474 Initialization File (-ininame) startup parameter 471 -inp startup parameter 472 Input Characters (-inp) startup parameter 472 Integrity database 467, 4139 Index6

L
-L startup parameter 478 -l startup parameter 479 Language (-lng) startup parameter 482 Large transactions effect on lock table 478 -ld startup parameter 480 List users PROSHUT command 219

Index -lkwtmo startup parameter 481 -lng startup parameter 482 Local Buffer Size (-l) startup parameter 479 Lock Table Entries (-L) startup parameter 478 Lock Timeout (-lkwtmo) startup parameter 481 Locking -NL startup parameter 4109 Log Entry Types (-logentrytypes) startup parameter 483 Log File Code Page (-cplog) startup parameter 435 Log files setting maximum size 417 Log Threshold (-logthreshold) startup parameter 489 -logentrytypes startup parameter 483 Logging Level (-logginglevel) startup parameter 487 -logginglevel startup parameter 487 Logical Database Name (-ld) startup parameter 480 -logthreshold startup parameter 489 Manual Server (-m2) startup parameter 492 Manual Server server type 492 Maximum Clients per Server (-Ma) startup parameter 494 Maximum Dynamic Server Port (-maxport) startup parameter 495 Maximum Memory (-mmax) startup parameter 4100 Maximum Private Buffers per Connection (-Bpmax) startup parameter 419 Maximum Servers (-Mn) startup parameter 4101 Maximum Servers per Broker (-Mpb) startup parameter 4103 -maxport startup parameter 495 MBPRO command 28 Memory server startup parameters 315 shared 4106 startup parameter 4100 Merge Number (-TM) startup parameter 4171 Message Buffer Size (-Mm) startup parameter 499 Messages system failure 468 -Mf startup parameter 496 -Mi startup parameter 497 Minimum Clients per Server (-Mi) startup parameter 497 Minimum Dynamic Server (-minport) startup parameter 498

M
-m1 startup parameter 491 -m2 startup parameter 492 -m3 startup parameter 493 -Ma startup parameter 494

Index7

OpenEdge Deployment: Startup Command and Parameter Reference -minport startup parameter 498 -Mm startup parameter 499 -mmax startup parameter 4100 -Mn startup parameter 4101 -Mp startup parameter 4102 -Mpb startup parameter 4103 MPRO command 29 -Mr startup parameter 4105 -Mxs startup parameter 4106 No Host Verify (-nohostverify) startup parameter 4112 No kill users (-bn) startup parameter PROSHUT command 219 No Lock (-NL) startup parameter 4109 No Session Cache (-nosessioncache) startup parameter 4115 No Session Reuse (-nosessionreuse) startup parameter 4116 -noautoreslist startup parameter 4110 -nochkttnames startup parameter 4111 -nohostverify startup parameter 4112 -noindexhint startup parameter 4113 -nojoinbysqldb startup parameter 4114 -nosessioncache startup parameter 4115 -nosessionreuse startup parameter 4116 -noSQLbyserver startup parameter 4117 NT Event Log specifying level of information 455 Number of Databases (-h) startup parameter 464 Number of Log Files to Keep (-numlogfiles) startup parameter 4119 Number of Users (-n) startup parameter 4107 -numdec startup parameter 4118 Numeric format changing 454, 4118, 4120 -numlogfiles startup parameter 4119 -numsep startup parameter 4120

N
-N startup parameter 219 -n startup parameter 4107 -nb startup parameter 4108 Nested Blocks (-nb) startup parameter 4108 Network Type (-N) startup parameter PROSHUT command 219 Networks connecting over wide area 423 server startup parameters 320 newkywd file 475 -NL startup parameter 4109 No Auto Result-list (-noautoreslist) startup parameter 4110 No Check Temp-table Names (-nochkttnames) startup parameter 4111 No Crash Protection (-i) startup parameter 467

Index8

Index

O
-o startup parameter 4121 -ojmode startup parameter 4123 Outer-join Mode (-ojmode) startup parameter 4123 OUTPUT TO PRINTER statement startup parameter 4121

Physical Database Name (-db) startup parameter 445 location 312 -pinshm startup parameter 4129 -plm startup parameter 4130 -pls startup parameter 4131 -populate startup parameter 4132 -properties startup parameter 4133

P
-P startup parameter 4124 -p startup parameter 26, 28, 4125 Page writer, see also Asynchronous page writer -param startup parameter 4126 Parameter (-param) startup parameter 4126 Parameter File (-pf) startup parameter 14, 4128 Parameter files 13 creating 15 editing 15 format 16 invoking 14 specifying 14 Password (-P) startup parameter 4124 Pending Connection Time (-PendConnTime) startup parameter 4127 Performance -noautoreslist startup parameter 4110 server startup parameters 315 -pf startup parameter 4128

Print Code Page (-cpprint) startup parameter 436 Printer (-o) startup parameter 4121 Private Read-only Buffers (-Bp) startup parameter 418 PRO command 210 PROAIW command 211 PROAPW command 212 PROBIW command 213 PROBRKR command 214 Procedure Editor startup commands UNIX and Windows 23 Windows 24 Processes cleaning up 222 PROLIB Memory (-plm) startup parameter 4130 PROLIB Swap (-pls) startup parameter 4131 PROQUIET Command 215 PROSERVE command 216 PROSHUT command 218

Index9

OpenEdge Deployment: Startup Command and Parameter Reference PROWDOG command 222 PROWIN command 223 Proxy Host (-proxyhost) startup parameter 4134, 4136 Proxy Password (-proxyPassword) startup parameter 4135 Proxy Port (-proxyport) startup parameter 4136 Proxy Userid (-proxyUserid) startup parameter 4137 -proxyhost startup parameter 4134, 4136 -proxyPassword startup parameter 4135 -proxyport startup parameter 4136 -proxyUserid startup parameter 4137 Recovery Log Threshold (-bithold) startup parameter 417 Remote databases starting a DataServer broker 214 Reread Nolock (-rereadnolock) startup parameter 4141 -rereadnolock startup parameter 4141 -rg startup parameter 4143 -RO startup parameter 4144 -rq startup parameter 4145 -rr startup parameter 4146 Run 4GL Client (-rg) startup parameter 4143 Run Query Client (-rq) startup parameter 4145 Run Run-time client (-rr) startup parameter 4146 -rx startup parameter 4147

Q
-q startup parameter 4138 Quick Request (-q) startup parameter 4138

R
-r startup parameter 4139 R-code In Code Page (-cprcodein) startup parameter 437 R-code Out Code Page (-cprcodeout) startup parameter 438 -rand startup parameter 4140 Read-only (-RO) startup parameter 4144 Record Buffer Size (-Mr) startup parameter 4105 Record fragmentation 499

S
-S startup parameter 219, 4148 -s startup parameter 4150 Save Temp Files (-t) startup parameter 4168 Schema Cache File (-cache) startup parameter 423 Schema Field Cache Size (-fc) startup parameter 458 Search for files speeding up 4138 Search path limiting 4138

Index10

Index Secondary Login Broker (-m3) startup parameter 493 Secondary Login Broker server type 493 Segment Statistics (-yd) startup parameter 4184 SELECT Pass Through Disable (-noSQLbyserver) startup parameter 4117 Semaphore Sets (-semsets) startup parameter 4151, 4152 -semsets startup parameter 4151, 4152 Server Join (-nojoinbysqldb) startup parameter 4114 Server startup parameters buffers 315 networks 320 performance 315 server type specification 318 statistic collection specification 319 Server-type startup parameters 318 Servers controlling number spawned for one protocol 4102 defined 12 types 491, 492 Servers per Protocol (-Mp) startup parameter 4102 -ServerType startup parameter 4153 Service Name (-S) startup parameter 4148 PROSHUT 219 Session Timeout (-sessiontimeout) startup parameter 4154 -sessiontimeout startup parameter 4154 Shared memory overflow area 4106 Shared-memory Overflow Size (-Mxs) startup parameter 4106 Shutdown commands 218 Single-user Mode (-1) startup parameter 42 -Sn startup parameter 4155 Sorting block size 4170 merge number parameter 4171 Source code encrypted 4147 Spawning servers manually 492 Speed Sort (-TB) startup parameter 4170 Spin Lock Retries (-spin) startup parameter 4156 -spin startup parameter 4156 Spooling startup parameters 4121 SQL Open Cursors (-SQLCursors) startup parameter 4158 SQL Sorting Memory (-SQLTempBuff) startup parameter 4161 SQL Sorting on Disk(-SQLTempDisk) startup parameter 4162 SQL Stack Size (-SQLStack) startup parameter 4159 SQL Statement Cache Size (-SQLStmtCache) startup parameter 4160 SQL Temp Table Data Page(-SQLTempPgSize) startup parameter 4163 -SQLCursors startup parameter 4158

Index11

OpenEdge Deployment: Startup Command and Parameter Reference -SQLStack startup parameter 4159 -SQLStmtCache startup parameter 4160 -SQLTempBuff startup parameter 4161 -SQLTempDisk startup parameter 4162 -SQLTempPgSize startup parameter 4163 -ssl startup parameter 4164 SSL-based Connection (-ssl) startup parameter 4164 Stack defined 4150, 4159 overflow errors 4150, 4159 Stack Size (-s) startup parameter 4150 Starting a DataServer broker 214 Starting OpenEdge graphical mode 223 multi-user 29 batch mode 28 server 216 single-user 210 batch mode 26 Startup .pf file 13 Startup commands about 12 syntax 22 tasks you can perform 23 Startup parameters about 12, 32 buffers 315 changing defaults 32 client connection 312 client database connection 312 client international 38 client session parameters 32 client session statistics 310 database server 315 database server international 318 for spooling output 4121 Index12 memory 315 networks 320 performance 315 server type specification 318 statistic collection specification 319 usage categories 32 windows session 311 Startup Procedure (-p) startup parameter 4125 Stash area defined 4165 Stash Area (-stsh) startup parameter 4165 Statistic Collection startup parameters 319 Statistics tracking access 412, 417 Statistics (-y) startup parameter 4180, 4181 Statistics with Cross-reference (-yx) startup parameter 4186 Statistics with CTRL-C (-yc) startup parameter 4183 Stream Code Page (-cpstream) startup parameter 439 -stsh startup parameter 4165 System failures message for full-integrity Progress session 468 message for no-integrity Progress session 468

T
-T startup parameter 4166 -t startup parameter 4168 Table Base (-basetable) startup parameter 414

Index Table Limit (-tablelimit) startup parameter 4169 -tablerangesize startup parameter 4169 -TB startup parameter 4170 Temporary Directory (-T) startup parameter 4166 Temporary files 4168 Terminal Code Page (-cpterm) startup parameter 440 Thousands Separator (-numsep) startup parameter 4120 Threshold Stall (-bistall) startup parameter 416 -TM startup parameter 4171 -tok startup parameter 4172 Token (-tok) startup parameter 4172 -trig startup parameter 4173 Trigger Location (-trig) startup parameter 4173 Type of Server to Start (-ServerType) startup parameter 4153 Use OS Locale (-useOsLocale) startup parameter 4175 -useOsLocale startup parameter 4175 User ID (-U) startup parameter 4174 Users maximum number 4107

V
-v6colon startup parameter 4176 -v6q startup parameter 4177 Validation using dictionary and help 450 Version 6 Colon (-v6colon) startup parameter 4176 Version 6 Query (-v6q) startup parameter 4177 VLM Page Table Entry Optimization (-Mpte) startup parameter 4104

W
-Wa -wpp startup parameter 4178, 4179 Watchdog process, see also PROWDOG utility Wide area networks connecting 423 Windows Passthrough Printing (-Wa -wpp) startup parameter 4178, 4179 Windows session client startup parameters 311

U
-U startup parameter 4174 Usage categories startup parameters 32 Usage reporting statistics with CTRL-C (-yc) parameter 4183 -y startup parameter 4181

Index13

OpenEdge Deployment: Startup Command and Parameter Reference

Y
-y startup parameter 4180, 4181 -yc startup parameter 4183 -yd startup parameter 4184

Year two-digit 4188 -yr4def startup parameter 4185 -yx startup parameter 4186 -yy startup parameter 4188

Index14