Universal Data Mover Manager Configuration Options
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. | |