**** Selector disabled, use WEB SET OPTION and WEB GET OPTION commands ****

**** Selector disabled, use WEB SET OPTION and WEB GET OPTION commands ****

**** Selector disabled, use WEB SET OPTION and WEB GET OPTION commands ****

**** Selector disabled, use WEB SET OPTION and WEB GET OPTION commands ****

**** Selector disabled, use WEB SET OPTION and WEB GET OPTION commands ****

**** Selector disabled ****

Deprecated

Deprecated

**** Selector disabled ****

Scope: 4D Server, 4D remote
Kept between two sessions: No
Possible values: 0 or from 1 to X (0 = do not record, 1 to X = sequential number, added to the file name).
Description: Starts or stops the recording of standard requests received by 4D Server (excluding Web requests). By default, the value is 0 (requests not recorded).
4D Server lets you record each request received by the server machine in a log file. When this mechanism is enabled, two files are created in the Logs folder of the database. They are named 4DRequestsLogServer_X.txt and 4DRequestsLog_ProcessInfoServer_X.txt on the server, and 4DRequestsLog_X.txt and 4DRequestsLog_ProcessInfo_X.txt on the remote, where X is the sequential number of the log. Once a file has reached a size of 10 MB, it is closed and a new one is generated, with an incremented sequential number. If a file of the same name already exists, it is replaced directly. You can set the starting number of the sequence using the value parameter. These text files store various information concerning each request in a simple tabbed format: time, process number, size of request, processing duration, etc. For more information on the 4DRequestsLog files, please refer to the Description of log files section.

• If you pass a positive value in the value parameter, you set a global and permanent timeout: the new value is applied to all process and is stored in the preferences of the 4D application (equivalent to change in the Preferences dialog box).
• If you pass a negative value in the value parameter, you set a local and temporary timeout: The new value is applied to the calling process only (the other processes keep the default values) and is reset to default as soon as the server receives any signal of activity from the client — for example, when the operation is finished. This option is useful for managing long operations initiated by 4D plug-ins.

• 0 (default value): no dynamic synchronization (synchronization request is ignored)
• 1: automatic dynamic synchronization
• 2: display of a dialog box on the client machines, with the possibility of allowing or refusing synchronization.

Scope: 4D local, 4D Server.
Kept between two sessions: No
Possible values: Any integer value, 0 = keep all logs
Description: Maximum number of files to keep in rotation for each type of log. By default, the 50 most recent files are kept. If you pass a value X, only the X most recent files are kept, with the oldest being erased automatically when a new one is created. This setting applies to all log files, i.e. request logs (selectors 28 and 45), debug log (selector 34), events log (selector 79), Web logs (selectors 29 and 84 of the WEB SET OPTION command), etc.

Scope: Remote 4D machine
Kept between two sessions: No
Possible values: 0 or from 1 to X (0 = do not record, 1 to X = sequential number, attached to file name).
Description: Starts or stops recording of standard requests carried out by the 4D client machine that executed the command (excluding Web requests). By default, the value is 0 (no recording of requests).
4D lets you record the log of requests carried out by the client machine. When this mechanism is activated, two files are created on the client machine, in the Logs subfolder of the local folder of the database. They are named 4DRequestsLog_X.txt and 4DRequestsLog_ProcessInfo_X.txt, where X is the sequential number of the log. Once the file 4DRequestsLog has reached a size of 10 MB, it is closed and a new one is generated, with an incremented sequential number. If a file with the same name already exists, it is directly replaced. You can set the starting number for the sequence using the value parameter.
These text files store various information concerning each request in a simple tabbed format: time, process number, size of request, processing duration, etc. For more information on the 4DRequestsLog files, please refer to the Description of log files section.

Scope: 4D application
Kept between two sessions: No
Description: Starts or stops the sequential recording of programming events for the current process in a separated log file. This log is similar to the Debug log recording (selector 34) but focuses on the current process only. The log file name includes the letter "p" and the process number: 4DDebugLog[_pN_n].txt, where N is the process unique ID. 
For more information about this format and on the use of the 4DDebugLog file, please refer to Description of log files in the Design Reference. 
Notes: 

• This selector is provided solely for the purpose of debugging and should be used with care. In particular, it must not put into production since it can have an impact on the application performance. 
• You can use both Debug log recording and Current process debug log recording selectors simultaneously, in which case the current process actions will not be logged in the main log file. 

Scope: 4D application
Kept between two sessions: No
Description: Starts or stops the sequential recording of events occurring at the 4D programming level in the 4DDebugLog[_n].txt file or 4DDebugLogServer[_n].txt (where _n is the segment number of the file and Server is added to the file name when generated on the server). 

Two modes are available:
- Standard mode provides a basic view of events and the file is automatically placed in the Logs subfolder of the database, next to the structure file. Execution times are expressed in milliseconds with the "< ms" value displayed when an operation lasts less than one millisecond. 
- Tabbed mode provides additional information and uses a more compact, tabbed format in the file. Execution times are expressed in microseconds.
Possible values: Longint containing a bit field: value = bit1(1)+bit2(2)+bit3(4)+bit4(8)+…).
- Bit 0 (value 1) requests to enable the file (note that any other non-null value also enables it as well)
- Bit 1 (value 2) requests call parameters to commands and (interpreted mode only) methods
- Bit 2 (value 4) enables tabbed format.
- Bit 3 (value 8) disables immediate writing of each operation on disk (enabled by default). Immediate writing is slower but more effective, for example for investigating causes of a crash. If you disable this mode, the file contents are generated more quickly.
- Bit 4 (value 16) disables recording of plug-in calls (enabled by default).
- Bit 5 (value 32) disables member function logging.
Examples:
SET DATABASE PARAMETER (34;1) // enables standard mode without parameters, with runtimes
SET DATABASE PARAMETER (34;2) // enables standard mode with parameters and runtimes
SET DATABASE PARAMETER (34;2+4) // enables tabbed mode with parameters and runtimes
SET DATABASE PARAMETER (34;0) // disables file
For any type of interpreted or compiled 4D application (4D all modes, 4D Server, 4D Volume Desktop), you can avoid having a file record too much information by:
- restricting the 4D commands that are examined by using Log command list (selector 80), or
- restricting it to the current process only with Current process debug log recording (selector 111). This will add the letter "p" and the process number to the file name: 4DDebugLog[_pn_n].txt  or 4DDebugLogServer[_pn_n].txt
For more information about this format and on the use of the 4DDebugLog file, please refer to the Description of log files section..
Note: This selector is provided solely for the purpose of debugging and should be used with care since it can impact the application performance. 

Scope: 4D application
Kept between two sessions: No
Description: Level(s) of messages to be included in the diagnostic log when enabled (see selector Diagnostic log recording). Each level designates a category of diagnostic messages and automatically includes more important categorie(s). For a description of categories, see Diagnostic log levels section on developer.4d.com. 
Possible values: One of the following constants (Log info by default):

• Log trace: activates ERROR, WARN, INFO, DEBUG, TRACE (most detailed level)
• Log debug: activates ERROR, WARN, INFO, DEBUG 
• Log info: activates ERROR, WARN, INFO (default)
• Log warn: activates ERROR, WARN
• Log error: activates ERROR (least detailed level)

Scope: 4D application
Kept between two sessions: No
Possible values: 0 or 1 (0 = do not record, 1 = record)
Description: Starts or stops recording of the 4D diagnostic file. By default, the value is 0 (do not record).
4D can continuously record a set of events related to the internal application operation into a diagnostic file. Information contained in this file is intended for the development of 4D applications and can be analyzed with the help of the 4D tech support (for more information, please refer to the Description of log files section on developer.4d.com). When you pass 1 in this selector, a diagnostic file is automatically created (or opened) in the database Logs folder. The file is named 4DDiagnosticLog_X.txt (or 4DDiagnosticLogServer_X.txt if generated on the server). Once this file reaches a size of 10 MB, it is closed and a new file is generated, with an incremented sequence number X.
Note that you can include custom information in this file using the LOG EVENT command.

Scope: 4D application 
Kept between two sessions: No
Description: Activation mode of Direct2D under Windows.
Possible values: One of the following constants (mode 3 by default):
Direct2D Disabled (0): Direct2D mode is not enabled and the database functions in the previous mode (GDI/GDIPlus).
Direct2D Hardware (1): Use Direct2D as graphics hardware context for entire 4D application. If this context is not available, use Direct2D graphics software context.
Direct2D Software (3) (Default mode): Beginning with Windows 7, use Direct2D graphics software context for entire 4D application.
Warning: This selector is provided for debugging purposes only. Since several 4D features rely on Direct2D, it must not be disabled in deployed applications. Only the default mode (Direct2D Software) is approved for deployed applications. 

Scope:4D application unless value is negative
Kept between two sessions: No
Possible values: Whole value expressing a duration in seconds. The value can be positive (new connections) or negative (existing connections). By default, the value is 20.
Description: Maximum period of inactivity (timeout) for connections to both the 4D database engine and the SQL engine, as well as, in ServerNet mode (new network layer), to the 4D application server. When an idle connection reaches this limit, it is automatically put on standby, which freezes the client/server session and closes the network socket. In the server administration window, the state of the user process is indicated as "Postponed". This functioning is completely transparent for the user: as soon as there is new activity on the connection which is on standby, the socket is automatically reopened and the client/server session is restored.
On the one hand, this setting lets you save resources on the server: connections on standby close the socket and free up a process on the server. On the other hand, it lets you avoid losing connections due to the closing of idle sockets by the firewall. For this, the timeout value for idle connections must be lower than that of the firewall in this case.
If you pass a positive value in value, it applies to all new connections in all the processes. If you pass a negative value, it applies to connections that are open in the current process. If you pass 0, idle connections are not subjected to a timeout.
This parameter must be set on the client side. Usually, you do not need to change this value.

Scope: 4D local, 4D Server
Kept between two sessions: No
Possible values: 0 or from 1 to X (0 = do not record, 1 to X = sequential number, added to the file name). By default, the value is 0 (IMAP exchanges not recorded).
Description: Starts or stops the recording of exchanges between 4D and the IMAP server, when a transporter object is processed through IMAP_transporter.getMail( ) or IMAP_transporter.checkConnection( ). By default, the value is 0 (exchanges not recorded). When this mechanism is enabled, a log file is created in the Logs folder of the database. It is named 4DIMAPLog_X.txt, where X is the sequential number of the log. Once the file 4DIMAPLog has reached a size of 10 MB, it is closed and a new one is generated, with an incremented sequential number. If a file of the same name already exists, it is replaced directly. You can set the starting number of the sequence using the value parameter. By default, all files are kept, but you can control the number of files to keep using the Circular log limitation parameter.
For more information on the 4DIMAPLog_X.txt files, please refer to the Description of log files section.

Note: You can only use this selector with the Get database parameter command and its value cannot be set.
Scope: 4D application
Description: Returns 1 if the current database architecture is a project, and 0 otherwise. For more information, please refer to Project vs binary database section.

Note: You can only use this selector with the Get database parameter command and its value cannot be set.
Scope: 4D application
Description: Returns 1 if the host database architecture is a project, and 0 otherwise. For more information, please refer to Project vs binary database section.

Note: You can only use this selector with the Get database parameter command and its value cannot be set.
Scope: 4D application
Description: Returns 1 if the host project file/structure file is writable, and 0 if it is read-only.

Scope: Current 4D machine
Kept between two sessions: n/a
Description: Returns the version number of the LDAP library in the 4D application on the current machine. (Read only)

Scope: Current 4D machine
Kept between two sessions: n/a
Description: Returns the version number of the SASL library in the 4D application on the current machine. (Read only)

Scope: Current 4D machine
Kept between two sessions: n/a
Description: Returns the version number of the libzip library in the 4D application on the current machine. (Read only)

Scope: 4D application
Kept between two sessions: No
Possible values: String containing a list of 4D command numbers to record (separated by semi-colons) or "all" to record all the commands or "" (empty string) to record none of them or prefixed by "-" to exclude specific commands.
Description: List of 4D commands to record in or exclude from the debugging file (see selector 34, Debug Log Recording). By default, all 4D commands are recorded.
This selector restricts the quantity of information saved in the debugging file by limiting the 4D commands whose execution you want to record or exclude from recording. For example, you can write:

See selector 86 (Diagnostic log level)

See selector 86 (Diagnostic log level)

See selector 86 (Diagnostic log level)

See selector 86 (Diagnostic log level)

See selector 86 (Diagnostic log level)

Scope: 4D Server, 4D Web Server and 4D SQL Server
Kept between two sessions: No
Description: Used to specify the minimum Transport Layer Security (TLS) version, which provides data encryption and authentication between applications and servers. Connection attempts from clients supporting only versions below the minimum will be rejected. The setting is applied globally to the network layer. Once modified, the server must be restarted to use the new value.
Default value: TLSv1_3
Possible values:

• TLSv1_2 (TLS 1.2, introduced in 2008)
• TLSv1_3 (TLS 1.3, introduced in 2018)

NOTES:
- The 4D Internet Commands plugin uses a different network layer, therefore this selector will have no impact on its TLS version.
- This setting is ignored for your client server connections if your 4D Server uses the legacy network layer.

Scope: 4D application
Kept between two sessions: No
Possible values: 0 (resume logs), 1 (pause logs)
This selector allows to suspend/resume all logging operations started on the application (except ORDA logs). This feature can be useful to temporarily lighten the 4D application tasks or schedule logging operations. 

Scope: 4D application
Kept between two sessions: No
Values: Positive long integer type value. By default, the value is 500.
Description: Maximum number of requests accepted by the PHP interpreter. When this maximum number is reached, the interpreter returns errors of the "server busy" type. For security or performance reasons, you can modify this value. This parameter can also be modified globally for all the machines via the Database Settings. For more information about this parameter, please refer to the FastCGI-PHP documentation.
Note: On the 4D side, these parameters are applied dynamically; it is not necessary to exit 4D in order for them to be taken into account. On the other hand, if the PHP interpreter is already launched, it will be necessary to exit and relaunch it in order for these modifications to be taken into account.

Scope: 4D application
Kept between two sessions: No
Values: Positive long integer type value. By default, the value is 5.
Description: Number of child processes to be created and maintained locally by the PHP interpreter of 4D. For optimization reasons, the PHP interpreter creates and uses a set (pool) of system processes called "child processes" for processing script execution requests. You can vary the number of child processes according to the needs of your application. This parameter can also be modified globally for all the machines via the Database Settings. For more information about the PHP interpreter, please refer to the Design Reference manual.
Note: Under Mac OS, all the child processes share the same port. Under Windows, each child process uses a specific port number. The first number is the one set for the PHP interpreter; the other child processes increment the first one. For example, if the default port is 8002 and you launch 5 child processes, they will use ports 8002 to 8006.

Scope: 4D application
Kept between two sessions: No
Values : 0 = use internal interpreter, 1 = use external interpreter
Description: Value indicating whether PHP requests in 4D are sent to the internal interpreter provided by 4D or to an external interpreter. By default the value is 0 (use of interpreter provided by 4D). If you want to use your own PHP interpreter, for example in order to use additional modules or a specific configuration, pass 1 in value. In this case, 4D does not launch its internal interpreter in the case of PHP requests.
The custom PHP interpreter must have been compiled in FastCGI and be located on the same machine as the 4D engine. Note that in this case, you must manage the interpreter entirely; it will not be started nor stopped by 4D. This parameter can also be modified globally for all the machines via the Database Settings.

Scope: 4D local, 4D Server
Kept between two sessions: No
Possible values: 0 or from 1 to X (0 = do not record, 1 to X = sequential number, added to the file name). By default, the value is 0 (POP3 exchanges not recorded).
Description: Starts or stops the recording of exchanges between 4D and the POP3 server, when a transporter object is processed through POP3_transporter.getMail( ) or POP3_transporter.checkConnection( ). By default, the value is 0 (exchanges not recorded). When this mechanism is enabled, a log file is created in the Logs folder of the database. It is named 4DPOP3Log_X.txt, where X is the sequential number of the log. Once the file 4DPOP3Log has reached a size of 10 MB, it is closed and a new one is generated, with an incremented sequential number. If a file of the same name already exists, it is replaced directly. You can set the starting number of the sequence using the value parameter. By default, all files are kept, but you can control the number of files to keep using the Circular log limitation parameter.
For more information on the 4DPOP3Log_X.txt files, please refer to the Description of log files section.

• 0: Uses the current settings of the database (default value). In databases created starting with version 11.2 of 4D v11 SQL, "SQL joins" are always activated for queries by formula. In converted databases, this mechanism is not activated by default for compatibility reasons but can be implemented via a preference.
• 1: Always use automatic relations (= functioning of previous versions of 4D). In this mode, a relation is necessary in order to set the selection of a table according to queries carried out on another table. 4D does not do "SQL joins."
• 2: Use SQL joins if possible (= default operation of databases created in version 11.2 and higher of 4D v11 SQL ). In this mode, 4D establishes "SQL joins" for queries by formula when the formula is suited for it (with two notable exceptions, see the description of the QUERY BY FORMULA or QUERY SELECTION BY FORMULA command).

• In databases created with 4D v11 SQL, these commands are executed on the server.
• In converted databases, these commands are executed on the client machine, as in previous versions of 4D.
• In converted databases, a specific preference (Application/Compatibility page) can be used to globally modify the execution location of these commands.

Scope: 4D Server application
Kept between two sessions: No
Possible values: Positive longint
Description: Current remote connection sleep timeout in seconds. By default, the value is 172800 (48 hours). 
The sleep timeout is applied after a machine running a 4D remote application has switched to sleep mode. In this case, its session is maintained by 4D Server (see feature description). 4D Server checks every 5 minutes if any sleeping remote 4D has exceeded the sleep timeout, in which case it is dropped. Thus, the maximum allowed sleeping time is current sleep timeout + 300. In some cases, you might want to modify the sleep timeout, for example to release locked records/licenses more rapidely.  

Scope: Database
Kept between two sessions: Yes
Possible values: 0 (case not taken into account) or 1 (case-sensitive)
Description: Activation or deactivation of case-sensitivity for string comparisons carried out by the SQL engine.
By default, the value is 1 (case-sensitive): the SQL engine differentiates between upper and lower case and between accented characters when comparing strings (sorts and queries). For example “ABC”= “ABC” but “ABC” # “Abc” and "abc" # "âbc." In certain cases, for example so as to align the functioning of the SQL engine with that of the 4D engine, you may wish for string comparisons to not be case-sensitive (“ABC”=“Abc"="âbc"). 
Warning: Since this option modifies the database structure file and all processes, for performance reasons it is highly recommended to set it at database startup only.

This option can also be set in the Database settings.

Scope: 4D application
Kept between two sessions: No
Possible values: Sequence of strings separated by colons.
Description: Cipher list used by 4D for the secure protocol. This list modifies the priority of ciphering algorithms implemented by 4D. For example, you can pass the following string in the value parameter: "HIGH:!aNULL:!MD5:!3DES:!CAMELLIA:!AES128:!RSA:!DH:!RC4". For a complete description of the syntax for the ciphers list, refer to the ciphers page of the OpenSSL site.
This setting applies to the main Web server (excluding Web server objects), the SQL server, client/server connections, as well as the HTTP client and all the 4D commands that make use of the secure protocol. It is temporary (it is not maintained between sessions).
When the cipher list has been modified, you will need to restart the server concerned in order for the new settings to be taken into account.
To reset the cipher list to its default value (stored permanently in the SLI file), call the SET DATABASE PARAMETER command and pass an empty string ("") in the value parameter.
Note: With the Get database parameter command, the cipher list is returned in the optional stringValue parameter and the return parameter is always 0.

See selector 105 (Min TLS version).

• When used with SET DATABASE PARAMETER, defines a new value that will be available within the next opened database after 4D is restarted manually or using the OPEN DATABASE(*), OPEN DATA FILE, or RESTART 4D commands. 
• When used with Get database parameter, gets the currently available user parameter value, defined using a command line (see Command Line Interface), the .4DLink file (see Using a 4DLink file), or a call to SET DATABASE PARAMETER during the previous session.

(*) If SET DATABASE PARAMETER sets a User param value before a call to OPEN DATABASE with a .4DLink file that also contains a user-param xml attribute, 4D takes into account only the parameter provided by SET DATABASE PARAMETER.