Universal Data Mover Manager Configuration Options
- Former user (Deleted)
- Stonebranch (Deactivated)
Universal Data Mover Manager Configuration Options
This page provides links to detailed information on the configuration options available for use with the Universal Data Mover Manager.
The options are listed alphabetically, without regard to any specific operating system.
Configuration Options Information
For each configuration option, these pages provide the following information.
Description
Describes the configuration option and how it is used.
Usage
Provides a table of the following information:
Method | Syntax | IBM i | UNIX | Windows | z/OS |
Command Line, Short Form | <Format / Value> | ||||
Command Line, Long Form | <Format / Value> | ||||
Environment Variable | <Format / Value> | ||||
Configuration File Keyword | <Format / Value> | ||||
STRUDM Parameter | <Format / Value> |
Method
Identifies the different methods used to specify Universal Data Mover Manager configuration options:
- Command Line Option, Short Form
- Command Line Option, Long Form
- Environment Variable
- Configuration File Keyword
- STRUDM Parameter
Note
Each option can be specified using one or more methods.
Syntax
Identifies the syntax of each method that can be used to specify the option:
- Format: Specific characters that identify the option.
- Value: Type of value(s) to be supplied for this method.
Note
If a Method is not valid for specifying the option, the Syntax field contains n/a.
(Operating System)
Identifies the operating systems for which each method of specifying the option is valid:
- IBM i
- UNIX
- Windows
- z/OS
Values
Identifies all possible values for the specified value type.
Defaults are identified in bold type.
<Additional Information>
Identifies any additional information specific to the option.
Configuration Options List
The following table identifies all UDM Manager configuration options.
Option | Description |
|---|---|
Amount of data transferred in Network Fault Tolerant (NFT) mode before waiting for a data acknowledgement message from the receiver. | |
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. | |
Broker Interface Directory that specifies the location of the Universal Broker interface file. | |
File name / ddname of the PEM-formatted trusted CA X.509 certificates. | |
File name / ddname of UDM Manager's PEM-formatted X.509 certificate. | |
Number of days prior to certificate expiration to begin issuing informational messages about the expiration. | |
File name / ddname of the PEM-formatted CRL. | |
Character code page used to translate text data. | |
Specification to use the internal or external table for code page to CCSID mapping. | |
User-defined string. | |
Acceptable and preferred SSL/TLS cipher suites to use for the control session between UDM components. | |
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. | |
Encryption method to be used in a UDM transfer session if one is not specified by an encrypt parameter in the UDM open command. | |
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. | |
Displays a description of the command line options and their format. | |
Number of seconds of inactivity in an interactive UDM session after which the UDM Manager will close the session. | |
Directory in which UDM Manager is installed. | |
Default interval at which a keep alive message is sent from the UDM Manager to the transfer server(s). | |
Specification for merging standard out and standard error output streams from a remote command to the UDM transaction log. | |
Universal Message Catalog (UMC) file used to format messages. | |
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. | |
Default transfer mode type for UDM sessions. | |
List of message IDs representing Universal messages to be suppressed. | |
Expected network latency (in seconds). | |
Setting for whether or not UDM transfer sessions are network fault tolerant by default. | |
Directory name where the UDM Manager can find its message catalog and code page tables. | |
Level of fault tolerance for the open command. | |
Maximum number of attempts that will be made to establish a session by the open command. | |
Number of seconds that UDM will wait between each open retry attempt. | |
Host or IP address that UDM binds to when initiating outgoing connections to another UDM server. | |
Program Lock File directory that specifies the location of the UDM Manager program lock file. | |
ddname of Manager's PEM formatted RSA private key. | |
Password for the Manager's PRIVATE_KEY. | |
Specification for whether or not UDM will use proxy certificates in three-party transfer sessions if a certificate is supplied to the UDM Manager. | |
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. | |
TCP port number on the remote computer used for invoking UDM Server instances. | |
SAF certificate key ring name. | |
SAF key ring certificate label. | |
ddname from which to read a UDM script command file. | |
Script file containing UDM commands to execute. | |
Script options to pass into the script command file. | |
Size (in bytes) of the application's outgoing buffer for UDM. | |
Exit codes that cause Universal Broker to cancel the corresponding UDM Server of the exited UDM Manager. | |
Default size for file creation of physical files for both data and source file types. | |
SSL/TLS implementation. | |
Local Universal Broker with which the UDM Manager must register. | |
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.) | |
Maximum number of lines to write to the trace file. | |
Size of a wrap-around trace table maintained in memory. | |
Complete path to Universal Command for calls by the exec command. | |
File mode creation mask. | |
Complete path to USAP for calls by the execsap command. | |
Specification for whether or not the Universal Broker's X.509 certificate identity is verified. | |
Specification for writing of program version information and copyright. |