| Anchor | ||||
|---|---|---|---|---|
|
...
Provides a table of the following information:
Method | Syntax | IBM i | UNIX | Windows | z/OS |
Configuration File Keyword | <Format / Value> |
Method
| Anchor | ||||
|---|---|---|---|---|
|
...
The following table identifies all UDM Server configuration options.
Option | Description |
|---|---|
Specification for whether or not product activity monitoring events are generated. | |
Disposition of data set when an abnormal ending occurs. | |
Block size used for newly allocated data sets. | |
SMS data class used for newly allocated data sets. | |
Number of directory blocks for newly allocated partitioned data sets. | |
Data set organization used for newly allocated data sets. | |
Status of data sets being allocated for input. | |
Logical record length used for newly allocated data sets. | |
SMS management class used for newly allocated data sets. | |
Disposition of data set when normal ending occurs. | |
Status of existing data sets being allocated for output. | |
Primary space allocation used for newly allocated data sets. | |
Record format used for newly allocated data sets. | |
Secondary space allocation used for newly allocated data sets. | |
Space unit in which space is allocated for newly allocated data sets. | |
SMS storage class used for newly allocated data sets. | |
Unit used for newly allocated data sets. | |
Volume serial number used for newly allocated data sets. | |
Specification for whether or not the UDM rename command will succeed if the new file name provided in that command matches the name of an existing file. | |
Character code page used to translate text data. | |
Specification to use the internal or external table for code page to CCSID mapping. | |
Specification for whether or not data is compressed on all standard I/O files. | |
SSL/TLS cipher suites to use for data session between UDM primary and secondary servers. | |
Specification for whether or not the control session must be encrypted. | |
Events to be generated as persistent events. | |
Number of UDM transfer blocks transferred before a frame-sync message is sent with network fault tolerance turned on. | |
Directory in which UDM Server is installed. | |
Specification for how users are logged onto the system. | |
| MAX_SSL_PROTOCOL | Maximum SSL/TLS protocol level that will be negotiated and used for communications channels. |
Level of messages that UDM will write. | |
Minimum SSL/TLS protocol level that will be negotiated and used for communications channels. Note This option was introduced to IBM i in version 5.1.1.0. | |
List of message IDs representing Universal messages to be suppressed. | |
Expected network latency (in seconds). | |
Directory where the UDM Server message catalog and code page tables are located. | |
Host or IP address that UDM binds to when initiating outgoing connections to another UDM Server. | |
Number of attempts that the UDM Manager will make to re-establish a transfer session when a network fault occurs. | |
Number of seconds that UDM will wait between each successive attempt to re-establish a transfer session when a network fault occurs. | |
Size (in bytes) of the application's incoming buffer for UDM. | |
Size (in bytes) of the application's outgoing buffer for UDM. | |
Default size for file creation of physical files for both data and source file types. | |
Specification for whether or not to use TCP packet coalescing. | |
Size of the TCP receive buffer used for socket connections. | |
Size of the TCP send buffer used for socket connections. | |
(Renamed TCP_RECV_BUFFER.) | |
Name of directory that UDM Server uses for temporary files. | |
Name of directory that UDM Server uses for its trace files. | |
Maximum number of lines to write to the trace file. | |
Size of a wrap-around trace table maintained in memory. | |
File mode creation mask. | |
User security option. | |
User security option. |